This integration is the most versatile and allows it to added into any framework that exists out of Kualitee Test Management Tool. Since API’s are independent of Tools and Technologies, since they just need to be called and consumed. So if you integrate our API’s in your framework you can have your test cases reflect in runtime according to the execution.
The following are the pre-requisites of the API:
- Kualitee Domain is Setup
- You are logged into your Kualitee Domain
- You have the project and the relative Build, Module, Requirements, Test Scenario and Test Cases created and have those test cases added into your execution cycle.
Once you are done with the pre-requisites we can move to the next steps:
Step 1) Navigate to Test Lab
Step 2) Sub-Navigate to Test Execution
Upon navigating to the test case execution page you will be listed all the test cases which are added into the cycle of your project and they will show whether the test cases have passed or not.
Step 3) Click the Action Icon
Upon clicking the action icon of a particular test case you will be able to see the specific parameters and the api to be consumed.
The pop-up is as follows:
Step 4) The API Information
The Pop-Up will show all the specific details of the test case to be used in api. Following are the API Parameters:
- Project ID
- Test Case ID
- Test Case Name
The static API will remain the same which is: https://apiss.kualitee.com/api/v2/test_case_execution/change_status
You will be able to have access to all the parameters except for the token.
Step 5) Generating The Token for the API
Click on the user profile icon
Sub-navigate to Token and click on the API Token header
Upon clicking on generate new token a new token will be generated. With that you will have all the necessary things to implement the api.
Step 6) Consuming the API
Here we are using the postman to show the result of the API.
We will be executing the test case AUT_LOG_001 and changing its Status from NOW Run to Passed.
And with that you can see the test case status has changed.
Since every framework is different it’s better to call the API in its specific language or using a specific tool which you are already using in your framework but if you are using a BDD Approach we recommend you to implement it in you AFTER Hooks so the api is called and consumed after each test case is executed.