The TestResults page has to have the following functionality:

• Display a table with all the saved test results in the database
• Import new test results into the database
• Display a success/failure message to show the result of importing new results
• If the new imported test results have at least 1 failing tests, the row should have a red background
• If the new imported test results have at least 1 inconclusive tests, the row should have a yellow background
• Be able to delete test results from the table and have it update the database

Front end needs to be written in ReactJS.

Right now there are a lot of floating files in the root directory. They need to be placed in corresponding folders.

Right now, the way you choose which environment the tests run against is done by updating the url of the website.

This should be changed to have an environment setting instead.

Right now the user has to type in values when setting up a new test setting.

The user should be shown drop down lists where appropriate to set up new settings.

In order to avoid duplicate groups, there should be some "validation" to make sure no duplicate groups are being created.

The web app is currently done only using MVC 5.

The web app needs to be rewritten/migrated to be in ASP.NET Core MVC and ReadJs.

The TestCases page has to have the following functionality:

• The home page should display a table with all the saved test suites in the database
• Buttons on each row of suites to see details of suite or delete suite
• The details page should display a table with all the saved test cases belonging to that suite in the database
• Button on each row of cases to delete an individual test case
• Import new test suites and test cases if they are in the correct format
• If you try to delete a suite, you should see a page asking for confirmation before deleting the suite and all associated test cases
• If you try to delete a case, you should see a page asking for confirmation before deleting the individual case

Front end needs to be written in ReactJS.

Right now we run all available tests, but this might not be what the user wants to do every time.

A list of available tests should be displayed and the user should be able to choose which tests to run.

Find a way to store any screenshots of failing tests to be stored in the db. In the future, these will be displayed along the results in the web app.

• #34

In order to be able to get information to the React front-end, there needs to be an API that returns Json.

The Settings page has to have the following functionality:

• Display a table with all the saved configurations in the database
• Add a new configuration
• Generate a new configuration file for the UI Tests
• Kickoff the automated tests
• Stop the automated tests

Front end needs to be written in ReactJS.

Right now, there is no way to know which test cases were ran in any given test run.

Using the test cases that have been imported into the db, find a way to map the test cases and show which tests were included in each run.

Convert the project to use MS SQL Server 2017.

Also look into Flyway to manage db changes.

Using the historical data in the test runs section, find a way to show how often each test passes or fails.

Right now the user will get an error if they try to delete a test suite or a test case.

This should not happen, the user should be able to delete either one.

For now there are two projects in the repo: a version that runs on .Net Framework and the other that runs on .Net Core.

Once the .Net Core version has all the same features as the .Net Framework version does, it will be safe to delete.

This ticket depends on the following before this one can be completed:

• #29
• #30
• #31
• #33
• #34