Track Manual Tests
- Dominant language
- Java
- Stars
- 80
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
# Track manual tests
## Context
The FUNCTIONALITIES screen allows to keep track of test coverage by automatic tests.
Some functionalities cannot be automated.
For them, it would be nice to track manual tests.
## Expected
### Cartography : Edit
When editing a functionality, a new CLOB field would allow to enter one URL per line (one URL per manual test case):

### Cartography : New Column
In the CARTOGRAPHY screen, a new column will appear:

It will show the number of manual tests.
The filter should be able to show only functionalities with manual tests ("Y"), or only those without manual tests ("N"). +
Clicking one option will disable the other. +
Clicking the checked option will disable that filter.
The cell must be clickable (the number should be blue) to show the following popup:

Each link will open in a new tab (target blank).
### Coverage
When reporting coverage, each category will have a new "(including XXX manual tests)" indicator:

Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the FUNCTIONALITIES edit screen, the CARTOGRAPHY screen, and the coverage-reporting entry point. Trace how functionality data and automatic test coverage are stored and displayed before determining where the manual-test URLs and counts belong. Done means users can enter one URL per line, filter and open manual tests from CARTOGRAPHY, and see manual-test counts in coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100