-
Notifications
You must be signed in to change notification settings - Fork 35
Testcases
Testcase is the basic entity of the service.
It allows you to store description, preconditions, steps and expectations, key-value properties and attributes. Testcase may have linked tracker issues and comments.
Testcases have sequential numeric ids - like tickets in tracker systems.
Preconditions - actions that should be taken prior to test execution.
Attributes play crutial role. This is what allows testcases to be grouped in a testsuite tree.
Attribute has a key and a list of values. When we build the testsuite tree - we are determining attribute keys as tree level and attribute values as nodes. Lets have a look at the example.
TestCase A covers functionality "header", has severity "normal" and is suitable for OS "Windows".
TestCase A covers functionality "body", has severity "critical" and is suitable for OS "Linux" and "MacOS".
It would be a good idea to add attributes with corresponding keys to a testcase:
"Functionality", "Severity" and "OS".
Add corresponding values to the attributes of each testcase.
Now you can build testcase trees. Lets assume we want to group testcases first - by severity, second - by OS. We choose corresponding attribute keys in testcase filter - Severity and OS. As a result - we are getting a tree of testcases. The first level will contain severity groups - "Normal" and "Critical". The second level of the tree will contain "OS" - Linux, Windows and MacOS. Each terminal node will contain corresponding testcases.
Following this instructions a user can build any type of trees relying on attributes.
Attributes are also used to filter testcases. E.g. - if we want to see only *nix testcases - we can configure filter to show "OS" Linux and MacOs only - Windows will be filtered out.
Filters and groupings could be saved - those configurations are called "Test Suites".
It is important to remember - testSuite is just a grouping filter. If you remove or edit a testcase in testSuite - you'll affect the original testcase. Testcases are not being copied to new testSuites. On the other hand - if you'll create a testcase with corresponding attributes - it will appear in testsute immediately.
Using testsuites, grouping and filtering - you can create testLaunches.
Properties are just a key-value members of testCase. They are helpful for test automation and external executors.
Each step has a description and expectations. At least one of those fields is required to be filled.
ToDo: still in development This section allows users to communicate within a testcase - leave comments and express concerns.
ToDo: still in development This section allows to link a testCase with an issue in task/bug trakcker, shows the list of related issues. Data and functionality if provided by a configured tracker plugin.