Files
calminer/tests/integration
zwitschi 522b1e4105
Some checks failed
CI / test (push) Has been skipped
CI / build (push) Has been skipped
CI / lint (push) Failing after 15s
CI / deploy (push) Has been skipped
feat: add scenarios list page with metrics and quick actions
- Introduced a new template for listing scenarios associated with a project.
- Added metrics for total, active, draft, and archived scenarios.
- Implemented quick actions for creating new scenarios and reviewing project overview.
- Enhanced navigation with breadcrumbs for better user experience.

refactor: update Opex and Profitability templates for consistency

- Changed titles and button labels for clarity in Opex and Profitability templates.
- Updated form IDs and action URLs for better alignment with new naming conventions.
- Improved navigation links to include scenario and project overviews.

test: add integration tests for Opex calculations

- Created new tests for Opex calculation HTML and JSON flows.
- Validated successful calculations and ensured correct data persistence.
- Implemented tests for currency mismatch and unsupported frequency scenarios.

test: enhance project and scenario route tests

- Added tests to verify scenario list rendering and calculator shortcuts.
- Ensured scenario detail pages link back to the portfolio correctly.
- Validated project detail pages show associated scenarios accurately.
2025-11-13 16:21:36 +01:00
..

Lifecycle Integration Test Plan

Coverage Goals

  • Exercise end-to-end creation, update, and deletion flows for projects through both API endpoints and HTML form submissions to ensure consistency across interfaces.
  • Validate scenario lifecycle interactions (create, update, archive) including business rule enforcement and status transitions when performed via API and UI routes.
  • Confirm that redirect chains and rendered templates match expected destinations after each lifecycle operation.
  • Verify repository-backed statistics (counts, recency metadata) update appropriately after lifecycle actions to maintain dashboard accuracy.
  • Guard against regressions in unit-of-work transaction handling by asserting database state after success and failure paths within integration flows.

Happy-Path Journeys

  1. Project Management Flow

    • Navigate to the project list UI and confirm empty-state messaging.
    • Submit the new project form with valid data and verify redirect to the list page with the project present.
    • Perform an API-based update to adjust project metadata and check the UI detail view reflects changes.
    • Delete the project through the API and ensure the list UI reverts to the empty state.
  2. Scenario Lifecycle Flow

    • From an existing project, create a new scenario via the API and verify the project detail page renders the scenario entry.
    • Update the scenario through the UI form, ensuring redirect to the scenario detail view with updated fields.
    • Trigger a validation rule (e.g., duplicate scenario name within a project) to confirm error messaging without data loss.
    • Archive the scenario using the API and confirm status badges and scenario counts update across dashboard and project detail views.
  3. Dashboard Consistency Flow

    • Seed multiple projects and scenarios through combined API/UI interactions.
    • Visit the dashboard and ensure metric cards reflect the latest counts, active/draft status breakdowns, and recent activity timestamps after each mutation.
    • Run the lifecycle flows sequentially to confirm cumulative effects propagate to dashboard summaries and navigation badges.