canonical / canonical/charm-integration-testing
Log `DEBUG` level test suite logs a file that uploaded to swift
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 6
- Forks
- 1
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 96
Description
Info logging is nice to see on Test Observer, but the DEBUG level logs may sometimes be helpful, and it would be nice to look at these.
How should this work? Should it log to a file, or log to the JUnit?
Contributor guide
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 tracing how test-suite Info logs reach Test Observer and where uploaded files are handled. Compare the issue's two proposed destinations, a log file or JUnit output, and identify the existing entry points involved. Done means DEBUG logs are available through the agreed Test Observer output and the behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100