TIA for Manual Tests
Manual tests are supported throughout all of SeaLights' products, but while our coverage and TGA reports do not need to detect each particular manual test in order to show the full coverage and risk analytics, for the TIA to work properly, the system does need to learn about each of the manual tests separately.
Test detection
The first step in allowing the TIA tool to optimize manual tests is to allow the SeaLights engine to detect and learn about each separate manual test. There are three ways to achieve this:
Using the SeaLights chrome extension to report manual tests
Using the SeaLights manual tests wizard that is part of the Test Optimization page
Using the SeaLights API to report the manual tests from any testing platform
Option 1 - Use the Chrome Extension “Manual Tests”
Installing and launching the SeaLights chrome extension
Go to your Chrome store and search for “SeaLights Chrome extension”
Download the extension to your local computer. You will need to do this for all computers used by your manual testers.
If the extension is not automatically pinned to your bar, it is advised to pin it.
Copy the extension token from the SeaLights UI by (a) going to the setting page, and then (b) under “integrations” click on “browser extension token
Copy the token by clicking on the “copy token to clipboard”
Open the extension setting (a) and paste the token (b)
Running tests using the SeaLights Chrome extension
The Chrome extension is designed to be used in parallel to the performance of the manual test.
While the manual tester is performing the test, they should also enter relevant information about the test to the extension.
There are three ways to ‘let the extension know’ which test is being performed by the tester:
Enter a single test name to the extension each time
Upload tests from a CSV file
Use the tests recommended by the TIA engine for the build that is being tested
In any of the options, once the test is performed, it is registered by the system in the same way and is used for the production of recommendations for the next build in the branch
Entering a single test name to the extension each time
Click on the SeaLights Chrome extension icon and on the “Start manual test” line.
The default setting is to report the tests according to App / Branch / Build. Make sure the information there is correct to the test being performed.
Choose the radio button “single test”
Enter the test stage, the test suite, and the test name. If the test was previously run and reported to SeaLights, an auto-complete will help you find it quickly.
5. Click on “Save”. This will minimize the extension as follows:
Uploading a list of tests from a CSV file
Click on the SeaLights Chrome extension icon and on the “Start manual test” line.
The default setting is to report the tests according to App / Branch / Build. Make sure the information there is correct to the test being performed.
Choose the radio button “test list” and than click on “Upload from file”
The file should be of a .csv format: first column should include a header and then a list of test names, each test name in a separate row. Example file is attached below.
After choosing a file and uploading it, you should see the list of all tests that the file contains. You are now able to:
Unclick a test that you do not wish to execute this time, by unselecting it’s checkbox
Enter a new one by clicking on the plus sign on the top of the page
Change the tests order by grabbing one and dragging it