@nextsparkjs/core 0.1.0-beta.1 → 0.1.0-beta.11

package/templates/contents/themes/default/tests/cypress/e2e/uat/billing/usage.bdd.md

@@ -1,218 +0,0 @@
----
-feature: Billing Usage Limits
-priority: high
-tags: [billing, usage, limits, resources, plans]
-grepTags: [uat, billing, usage]
-coverage: 7
-status: pending-permission-fix
----
-
-# Billing Page - Usage Limits
-
-> Tests for usage limits display including Free plan limits, Pro plan higher limits, Enterprise unlimited display, usage percentage, and progress indicators. **Note:** Currently skipped due to permission check issues.
-
-## Background
-
-```gherkin:en
-Given I am logged in as a team owner
-And I have navigated to the Billing settings page
-And usage information is available for my team
-```
-
-```gherkin:es
-Given estoy logueado como owner del team
-And he navegado a la pagina de configuracion de Billing
-And la informacion de uso esta disponible para mi team
-```
-
----
-
-## @test BILL-UAT-080: Free plan shows usage with limits
-
-### Metadata
-- **Priority:** Critical
-- **Type:** Regression
-- **Tags:** free, usage, limits
-- **Status:** SKIPPED (permission issue)
-
-```gherkin:en
-Scenario: Free plan displays usage against limits
-
-Given I am on a Free plan team
-When I visit the billing page
-Then I should see usage displayed (X / Y format)
-```
-
-```gherkin:es
-Scenario: Plan Free muestra uso contra limites
-
-Given estoy en un team con plan Free
-When visito la pagina de billing
-Then deberia ver el uso mostrado (formato X / Y)
-```
-
-### Expected Results
-- Usage section is visible
-- Usage shows current/limit format
-- Free plan limits are displayed
-
----
-
-## @test BILL-UAT-081: Usage shows current count
-
-### Metadata
-- **Priority:** Normal
-- **Type:** Regression
-- **Tags:** usage, count, display
-- **Status:** SKIPPED (permission issue)
-
-```gherkin:en
-Scenario: Usage shows current resource count
-
-Given I am on the billing page
-Then I should see my current usage numbers
-```
-
-```gherkin:es
-Scenario: Uso muestra conteo actual de recursos
-
-Given estoy en la pagina de billing
-Then deberia ver mis numeros de uso actuales
-```
-
-### Expected Results
-- Usage numbers are displayed
-- Format matches X / Y pattern
-- Numbers reflect actual resource count
-
----
-
-## @test BILL-UAT-082: Pro plan shows higher limits
-
-### Metadata
-- **Priority:** Normal
-- **Type:** Regression
-- **Tags:** pro, usage, limits
-- **Status:** SKIPPED (permission issue)
-
-```gherkin:en
-Scenario: Pro plan has higher limits than Free
-
-Given I am on a Pro plan team
-When I visit the billing page
-Then I should see higher usage limits
-```
-
-```gherkin:es
-Scenario: Plan Pro tiene limites mas altos que Free
-
-Given estoy en un team con plan Pro
-When visito la pagina de billing
-Then deberia ver limites de uso mas altos
-```
-
-### Expected Results
-- Pro plan limits are displayed
-- Limits are higher than Free tier
-- Usage section is visible
-
----
-
-## @test BILL-UAT-083: Enterprise plan shows Unlimited where applicable
-
-### Metadata
-- **Priority:** Normal
-- **Type:** Regression
-- **Tags:** enterprise, unlimited, limits
-- **Status:** SKIPPED (permission issue)
-
-```gherkin:en
-Scenario: Enterprise plan shows unlimited resources
-
-Given I am on an Enterprise plan team
-When I visit the billing page
-Then I should see "Unlimited" or very high limits
-```
-
-```gherkin:es
-Scenario: Plan Enterprise muestra recursos ilimitados
-
-Given estoy en un team con plan Enterprise
-When visito la pagina de billing
-Then deberia ver "Ilimitado" o limites muy altos
-```
-
-### Expected Results
-- Enterprise plan is displayed
-- Some resources show as unlimited
-- Billing page is visible
-
----
-
-## @test BILL-UAT-084: Usage display is visible on billing page
-
-### Metadata
-- **Priority:** Normal
-- **Type:** Regression
-- **Tags:** usage, section, visibility
-- **Status:** SKIPPED (permission issue)
-
-```gherkin:en
-Scenario: Usage section exists on billing page
-
-Given I am on the billing page
-Then I should see a usage section
-```
-
-```gherkin:es
-Scenario: Seccion de uso existe en pagina de billing
-
-Given estoy en la pagina de billing
-Then deberia ver una seccion de uso
-```
-
-### Expected Results
-- Billing main section is visible
-- Usage section exists
-- Usage information is displayed
-
----
-
-## @test BILL-UAT-085: Usage reflects actual resource count
-
-### Metadata
-- **Priority:** Normal
-- **Type:** Regression
-- **Tags:** usage, validation, accuracy
-- **Status:** SKIPPED (permission issue)
-
-```gherkin:en
-Scenario: Usage numbers are reasonable
-
-Given I am on the billing page
-Then the usage numbers should be non-negative integers
-And current usage should not exceed the limit
-```
-
-```gherkin:es
-Scenario: Numeros de uso son razonables
-
-Given estoy en la pagina de billing
-Then los numeros de uso deberian ser enteros no negativos
-And el uso actual no deberia exceder el limite
-```
-
-### Expected Results
-- Usage numbers are non-negative
-- Limit numbers are at least 1
-- Current usage does not exceed limit
-
----
-
-## Known Issues
-
-**Permission Check Issue (2025-12-28):**
-- Billing page redirects to /dashboard/settings for all users
-- `usePermission('settings.billing')` hook may not resolve correctly
-- TeamContext may not be properly hydrated during Cypress session restore
-- Investigation needed in: usePermission, TeamContext, permissionRegistry

package/templates/contents/themes/default/tests/cypress/e2e/uat/billing/usage.cy.ts

@@ -1,176 +0,0 @@
-/// <reference types="cypress" />
-
-import * as allure from 'allure-cypress'
-import { BillingPOM } from '../../../src/features/BillingPOM'
-import {
-  loginAsFreePlanUser,
-  loginAsProPlanUser,
-  loginAsEnterprisePlanUser
-} from '../../../src/session-helpers'
-
-/**
- * Billing Usage Limits UAT Tests
- *
- * Tests for usage limits display:
- * - Free plan limits (tasks, customers)
- * - Pro plan higher limits
- * - Enterprise unlimited display
- * - Usage percentage and progress bars
- *
- * Session: 2025-12-20-subscriptions-system-v2
- *
- * KNOWN ISSUE (2025-12-28):
- * These tests are skipped due to permission check issues.
- * The billing page redirects to /dashboard/settings even for owners.
- * Investigation needed:
- * - usePermission hook in billing/page.tsx may not be correctly resolving
- * - TeamContext may not be properly hydrated during Cypress session restore
- * - Related: settings.billing permission is configured for owner role only
- *
- * TODO: Debug usePermission('settings.billing') flow in Cypress context
- */
-
-describe('Billing Page - Usage Limits', {
-  tags: ['@uat', '@billing', '@usage']
-}, () => {
-  const billingPage = BillingPOM.create()
-
-  // ============================================================
-  // USAGE DISPLAY TESTS
-  // ============================================================
-  describe('Usage Limits Display', () => {
-    beforeEach(() => {
-      allure.epic('UAT')
-      allure.feature('Billing')
-      allure.story('Usage Limits')
-    })
-
-    it.skip('BILL-UAT-080: Free plan shows usage with limits (PENDING: permission issue)', () => {
-      allure.severity('critical')
-      allure.description(`
-        Scenario: Free plan displays usage against limits
-        Given I am on a Free plan team
-        When I visit the billing page
-        Then I should see usage displayed (X / Y format)
-
-        SKIPPED: Billing page redirects due to usePermission check failing
-      `)
-
-      loginAsFreePlanUser()
-      cy.visit('/dashboard', { timeout: 60000, failOnStatusCode: false })
-      cy.url().should('include', '/dashboard')
-      billingPage.visitBilling()
-      billingPage.assertUsageVisible()
-    })
-
-    it.skip('BILL-UAT-081: Usage shows current count (PENDING: permission issue)', () => {
-      allure.severity('normal')
-      allure.description(`
-        Scenario: Usage shows current resource count
-        Given I am on the billing page
-        Then I should see my current usage numbers
-
-        SKIPPED: Billing page redirects due to usePermission check failing
-      `)
-
-      loginAsFreePlanUser()
-      cy.visit('/dashboard', { timeout: 60000, failOnStatusCode: false })
-      cy.url().should('include', '/dashboard')
-      billingPage.visitBilling()
-      billingPage.getBillingMain().within(() => {
-        cy.contains(/\d+\s*\/\s*\d+/).should('exist')
-      })
-    })
-
-    it.skip('BILL-UAT-082: Pro plan shows higher limits (PENDING: permission issue)', () => {
-      allure.severity('normal')
-      allure.description(`
-        Scenario: Pro plan has higher limits than Free
-        Given I am on a Pro plan team
-        When I visit the billing page
-        Then I should see higher usage limits
-
-        SKIPPED: Billing page redirects due to usePermission check failing
-      `)
-
-      loginAsProPlanUser()
-      cy.visit('/dashboard', { timeout: 60000, failOnStatusCode: false })
-      cy.url().should('include', '/dashboard')
-      billingPage.visitBilling()
-      billingPage.assertUsageVisible()
-    })
-
-    it.skip('BILL-UAT-083: Enterprise plan shows Unlimited where applicable (PENDING: permission issue)', () => {
-      allure.severity('normal')
-      allure.description(`
-        Scenario: Enterprise plan shows unlimited resources
-        Given I am on an Enterprise plan team
-        When I visit the billing page
-        Then I should see "Unlimited" or very high limits
-
-        SKIPPED: Billing page redirects due to usePermission check failing
-      `)
-
-      loginAsEnterprisePlanUser()
-      cy.visit('/dashboard', { timeout: 60000, failOnStatusCode: false })
-      cy.url().should('include', '/dashboard')
-      billingPage.visitBilling()
-      billingPage.assertBillingPageVisible()
-      billingPage.getBillingMain().should('be.visible')
-    })
-
-    it.skip('BILL-UAT-084: Usage display is visible on billing page (PENDING: permission issue)', () => {
-      allure.severity('normal')
-      allure.description(`
-        Scenario: Usage section exists on billing page
-        Given I am on the billing page
-        Then I should see a usage section
-
-        SKIPPED: Billing page redirects due to usePermission check failing
-      `)
-
-      loginAsFreePlanUser()
-      cy.visit('/dashboard', { timeout: 60000, failOnStatusCode: false })
-      cy.url().should('include', '/dashboard')
-      billingPage.visitBilling()
-      billingPage.getBillingMain().should('be.visible')
-      billingPage.assertUsageVisible()
-    })
-
-    it.skip('BILL-UAT-085: Usage reflects actual resource count (PENDING: permission issue)', () => {
-      allure.severity('normal')
-      allure.description(`
-        Scenario: Usage numbers are reasonable
-        Given I am on the billing page
-        Then the usage numbers should be non-negative integers
-
-        SKIPPED: Billing page redirects due to usePermission check failing
-      `)
-
-      loginAsFreePlanUser()
-      cy.visit('/dashboard', { timeout: 60000, failOnStatusCode: false })
-      cy.url().should('include', '/dashboard')
-      billingPage.visitBilling()
-      billingPage.getBillingMain().within(() => {
-        cy.contains(/\d+\s*\/\s*\d+/).invoke('text').then((text) => {
-          const match = text.match(/(\d+)\s*\/\s*(\d+)/)
-          if (match) {
-            const current = parseInt(match[1])
-            const limit = parseInt(match[2])
-            expect(current).to.be.at.least(0)
-            expect(limit).to.be.at.least(1)
-            expect(current).to.be.at.most(limit)
-          }
-        })
-      })
-    })
-  })
-
-  // Document the skipped tests
-  it('documents billing usage tests pending due to permission check', () => {
-    cy.log('6 billing usage tests are pending due to usePermission hook issue')
-    cy.log('The billing page redirects to /dashboard/settings for all users')
-    cy.log('Investigation needed in: usePermission, TeamContext, permissionRegistry')
-    cy.wrap(true).should('be.true')
-  })
-})

package/templates/contents/themes/default/tests/cypress/e2e/uat/blocks/hero.bdd.md

@@ -1,124 +0,0 @@
----
-feature: Hero Block Component
-priority: high
-tags: [blocks, hero, page-builder, rendering]
-grepTags: [uat, b-hero, feat-page-builder, smoke]
-coverage: 3
-status: placeholder
----
-
-# Hero Block - UAT Tests
-
-> Tests for the Hero block component in page builder. Validates rendering, field behavior, and visual appearance. **Note:** These tests are placeholders to establish the block testing pattern.
-
-## Background
-
-```gherkin:en
-Given I am logged in as Owner (owner@nextspark.dev)
-And I have access to the page builder
-And pages with Hero blocks are available
-```
-
-```gherkin:es
-Given estoy logueado como Owner (owner@nextspark.dev)
-And tengo acceso al page builder
-And hay paginas con bloques Hero disponibles
-```
-
----
-
-## @test BLOCK-HERO-001: Hero block renders with default content
-
-### Metadata
-- **Priority:** Critical
-- **Type:** Smoke
-- **Tags:** rendering, default, structure
-- **Grep:** `@smoke`
-
-```gherkin:en
-Scenario: Hero block renders with default content
-
-Given I am on a page with a hero block
-When the page loads
-Then the hero block structure should render
-And default values should display correctly
-```
-
-```gherkin:es
-Scenario: Bloque Hero renderiza con contenido por defecto
-
-Given estoy en una pagina con un bloque hero
-When la pagina carga
-Then la estructura del bloque hero deberia renderizar
-And los valores por defecto deberian mostrarse correctamente
-```
-
-### Expected Results
-- Hero block container renders
-- Default structure is visible
-- Block displays without errors
-
----
-
-## @test BLOCK-HERO-002: Hero block displays title and subtitle
-
-### Metadata
-- **Priority:** Normal
-- **Type:** Regression
-- **Tags:** title, subtitle, fields
-
-```gherkin:en
-Scenario: Hero block displays title and subtitle
-
-Given I am on a page with a hero block
-When the block has title and subtitle configured
-Then the title should be visible
-And the subtitle should be visible
-```
-
-```gherkin:es
-Scenario: Bloque Hero muestra titulo y subtitulo
-
-Given estoy en una pagina con un bloque hero
-When el bloque tiene titulo y subtitulo configurados
-Then el titulo deberia estar visible
-And el subtitulo deberia estar visible
-```
-
-### Expected Results
-- Title field displays correctly
-- Subtitle field displays correctly
-- Typography and styling are applied
-
----
-
-## @test BLOCK-HERO-003: Hero block CTA buttons are configurable
-
-### Metadata
-- **Priority:** Normal
-- **Type:** Regression
-- **Tags:** cta, buttons, configuration
-
-```gherkin:en
-Scenario: Hero block CTA buttons are configurable
-
-Given I am editing a hero block
-When I configure CTA button settings
-Then the CTA buttons should reflect the configuration
-And button text and links should be customizable
-```
-
-```gherkin:es
-Scenario: Botones CTA del bloque Hero son configurables
-
-Given estoy editando un bloque hero
-When configuro los ajustes de botones CTA
-Then los botones CTA deberian reflejar la configuracion
-And el texto y enlaces de botones deberian ser personalizables
-```
-
-### Expected Results
-- CTA buttons are configurable
-- Button text can be customized
-- Button links can be set
-- Configuration changes are reflected in preview

package/templates/contents/themes/default/tests/cypress/e2e/uat/blocks/hero.cy.ts

@@ -1,56 +0,0 @@
-/// <reference types="cypress" />
-
-/**
- * Hero Block - UAT Tests
- *
- * Tests for the Hero block component in page builder.
- * Validates rendering, field behavior, and visual appearance.
- *
- * Tags: @uat, @b-hero, @feat-page-builder
- */
-
-import * as allure from 'allure-cypress'
-
-describe('Hero Block', {
-  tags: ['@uat', '@b-hero', '@feat-page-builder', '@smoke']
-}, () => {
-
-  beforeEach(() => {
-    allure.epic('UAT')
-    allure.feature('Page Builder')
-    allure.story('Hero Block')
-  })
-
-  describe('Block Rendering', () => {
-    it('BLOCK_HERO_001: Hero block renders with default content', () => {
-      allure.severity('critical')
-
-      // TODO: Implement actual test
-      // This is a placeholder to establish the block testing pattern
-      // 1. Navigate to a page with hero block
-      // 2. Verify block structure renders
-      // 3. Check default values display correctly
-
-      cy.log('Hero block rendering test - placeholder')
-      expect(true).to.be.true
-    })
-
-    it('BLOCK_HERO_002: Hero block displays title and subtitle', () => {
-      allure.severity('normal')
-
-      // TODO: Implement test for title/subtitle fields
-      cy.log('Hero block title/subtitle test - placeholder')
-      expect(true).to.be.true
-    })
-  })
-
-  describe('Block Fields', () => {
-    it('BLOCK_HERO_003: Hero block CTA buttons are configurable', () => {
-      allure.severity('normal')
-
-      // TODO: Test CTA button configuration
-      cy.log('Hero block CTA test - placeholder')
-      expect(true).to.be.true
-    })
-  })
-})