Decathlon / Decathlon/ara

Track Manual Tests

Open
#53 0 comments 0 reactions 0 assignees View on GitHub
Feature Request P2
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):

![image](https://user-images.githubusercontent.com/45944760/57127511-eff46400-6d90-11e9-9ad6-2e22611bb4c3.png)

### Cartography : New Column
In the CARTOGRAPHY screen, a new column will appear:
![image](https://user-images.githubusercontent.com/45944760/57127520-f7b40880-6d90-11e9-8627-379b339965d5.png)

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:
![image](https://user-images.githubusercontent.com/45944760/57127561-14504080-6d91-11e9-86e0-9360ed5a6dde.png)

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:
![image](https://user-images.githubusercontent.com/45944760/57127582-2205c600-6d91-11e9-85a6-2ee0fedfbb06.png)

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.