microsoft / microsoft/AzureTRE
Debugging API or E2E tests sources its own configuration
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 235
- Forks
- 192
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
Description
As an Azure TRE Developer
I want the ability to debug API or E2E tests without having to update the root configuration and just use the .env file which is in the folder
So that it will allow me to make changes to these tests more quickly and easily, without having to worry about affecting other parts of the system.
Acceptance criteria
- Debugging API or E2E tests doesn't require changes in root config.yaml
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 locating the API and E2E tests and comparing how they read the folder-level .env file with the root config.yaml. Trace the configuration used when debugging these tests; done means both API and E2E debugging work without modifying root config.yaml.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100