Testplan for <EPIC/FEATURE/CASE> Forside

| **Delivery** | |
|:-------------------------|:--------------------------------------------------|
| **Roadmap** | |
| **Involved teams** | @team-... |
| **Due date** | xx.xx.xxxx |
| **Test period** | xx.xx.xxxx - xx.xx.xxxx |

## Dependencies

| **Dependency** | **Owner** | **Status** |
|:-----------------------------------|:---------------------------|:-----------|
| | | |
| | | |
| | | |

## Functional tests
> ✅ OK, ⚠️ In progress, 🛑 Failed
> During test period run tests covering business needs and requirements listed here

| Scenario | Test data | Done by | Importance | Level | Status | Comment |
|------------|-----------|-------------|------------|---------|-------|---------|
| | | @... | High | | ✅ | |
| | | @... | Low | | 🛑 | |

## Non-functional tests

- Performance tests: Link to runs and documentation when needed
- Security tests: Link to documentation when needed

## Clarifications

| **Question** | **Answer** | **Date ** |
|:---------------------------------|:-----------------------------|:-----------|
| | | |
| | | |

## ⚠️ Out of scope
> List discussed functionality out of scope or that might be relevant in a later release

## :information_source: Useful links

### Sketches
### Architecture diagrams
### Test environment
### Testd ata
### Link to milestone

Start with the test-plan structure in the issue body, including the delivery details, dependencies, functional and non-functional tests, clarifications, scope, and useful links sections. Identify the missing EPIC/FEATURE/CASE and project-specific requirements before making changes; done means the plan is populated with agreed test coverage, owners, statuses, and references.

Written by the indexing model from the issue text.