project-chip / project-chip/certification-tool
[feature] Individual Log Generation for Each Test Case in Automation Tests
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 82
- Forks
- 47
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 17
Description
Feature description
Currently, when multiple automation tests are executed simultaneously, the logs are consolidated into a single file upon completion. However, for enhanced traceability and debugging purposes, it would be beneficial to have the capability to generate logs for each test case individually.
Use Cases
When multiple automation tests are executed simultaneously, the logs are typically consolidated into a single file upon completion. However, for Test events and official testing purposes, it's crucial to store each test case's log separately, identified by its respective TCID, instead of merging them into a unified log file. Therefore, the Test Harness (TH) must generate logs for each test case individually.
Test Cases
- Automated
- Semi-Automated
- Simulated
- Python
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Test Harness path that consolidates automation-test logs and review how TCIDs and the Automated, Semi-Automated, Simulated, and Python test cases enter it. Define the expected separate log output for each test case and verify that logs are no longer merged across those modes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, shell
- Domain
- testing-qa, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100