---
# System prepended metadata

title: ' Test Plan / Test Coverage Topics '

---

<h1> Test Plan / Test Coverage Topics </h1>

<h2>Automation</h2>


<h3>Point tests to specific environments (dev, staging, prod)</h3>
We need the ability to point automation tests to specific enviornments, as opposed to running them locally. 

**Pro's**
- [ ] Quickly test in the respective environemnt that the user will be engaging with. 
- [ ] Get a good feel of the level of quality when running smoke, regression and e2e tests.
- [ ] Pointing to these environments would take seconds to load, as opposed to ~5 min when running against your local environment.

**Con's**

 - [ ] TBD

---

 <h3>Automation Test Case Queue</h3>
 
I found myself confused as to what had already been automated, what was in progress and what had been completed. Was concerned I was going to duplicate someones work.
 
 We need a quick and simple way of viewing:
 - [ ] Which tests have been automated
     - [ ] script name
     - [ ] respective test cases covered

 - [ ] Which have not yet been automated
     - [ ] Maybe some way to claim them / queue them?
     - [ ] Perhaps Jira backlog tickets make sense / or a running list elsewhere ?

- [ ] Which tests need to be refactored / have been refactored?



---

<h3>Real Time Dashboards</h3>

We should look into creating / generating real time dashboards with test results.

- [ ] Do we have the ability to schedule test runs?
    - [ ] Similar to Jenkins ?
