Main TestCaddy Window
This is the initial screen of TestCaddy. The right-hand two thirds of the screen is a Work Area which provides the user with detailed data about the specific test they are viewing, while the left-hand third provides a tree-view of the various Test Sets available (grouped into Folders), and below that a tree-view of the active Test Set.
Every time a test is ‘run’ by a tester and they enter their test results for each step, TestCaddy saves the information in a History item. The parent test status is also updated to reflect the result of the last run (last History item). Tests can be paused and continued at a later stage. Every run is recorded, easily reviewed and certain aspects of the run can be edited at a later time.
Filtering allows easy in-line reporting by test status for the Active Test Set, e.g. a tester may turn on a filter to display only tests remaining to be run or to
highlight just Failed tests.
This is the initial stage of the Configuration Wizard. The first user to run TestCaddy can choose to install SQL Express or use an existing SQL server. This
becomes the central repository for all testing data, and other TestCaddy users simply enter the location and password of the central SQL server the first time they run TestCaddy. TestCaddy creates databases on the SQL server for each Product or line of testing. Each Product Database
contains test data for all testing Projects and sub Phases for that product.
Accessed from the Filter button on the Active Set section, this dialogue allows you to filter your tests to only show those that match a parameter you set, or any combination of parameters. Whether you want to see tests that have a status of passed AND are assigned to Freddie or to see tests that have the word “Connection” in them OR were last run on an environment of “WindowsXP”, TestCaddy’s filter gives you the choice. The filter dialogue is also available in the reports section and allows you to fine tune the data displayed on your graphs.
The Dashboard tab displays your choice of graphs, letting you see instantly the progress made on the selected tests or test set. The Dashboard by default shows the progress your whole team has made or your own personal user progress, although it is fully customisable to allow you to see whatever graphs you have created in the reports section. The Dashboard will automatically update depending on your Active Set selection, giving you instant tracking of your projects progress.
TestCaddy’s full Jira integration lets you create, monitor and link your tickets to your tests all without having to leave TestCaddy. With the fully functioning Jira browser within TestCaddy you get everything Jira has to offer as well as TestCaddy’s ability to link tests to tickets and the ability to create TestCaddy links from Jira back to TestCaddy. So whenever you view a test you are also shown all the tickets that correspond to it and you can even add TestCaddy links to your Jira tickets that will automatically take TestCaddy straight to that test.
Running a test
While running your test, TestCaddy gives you the option of using either a wysiwig editor or to type HTML straight into the HTML field. This lets you format your text using either our easy to use right click menu or hard coded HTML to communicate as effectively as possible to your tester. Then set each step as Passed, Failed etc as well as the run environment, version and build numbers for a full record of the way that test was run.
TestCaddy’s Custom Fields are split into two categories; Environment and General Custom Fields. Environment Custom Fields let you set for example the Operating System or SQL Server Version while all other Custom Fields are placed in the General Custom Field category. Custom Fields allow TestCaddy to be customised to match your process. Custom Field values can be set at different points in a tests life cycle, Example; a Test Lead, when assigning tests to testers, can use the Planning tab to set an Environment Custom Field of Operating System to the value of WindowsXP and set a General Custom Field of Reviewed Status to No. Later when running the Test, the Tester can record the Operating System that they actually ran the test on.