Test Cases
2.4.1. Definition
Different from traditional automation test script, akaAT Studio provides services to help you create script even faster by drag and drop actions. These steps are packaged into keyword groups for Web, Mobile, Windows, API, Database, Image, Core, Control, PDF and Random.
There are five kinds of test cases:
- "E2E test case" supports you to create and run scripts on multiple platforms
- "Web test case" supports you to create and run scripts on Web platform.
- "Mobile test case" supports you to create and run scripts on Mobile app.
- "Windows test case" supports you to create and run scripts for Windows app.
- "Jmeter test case" supports you to create, import and run jmeter scripts.
2.4.2. Screen description
| Object | Type | Description |
|---|---|---|
| Set up | Tab | The steps are meant to prepare for the main steps ofthe test case. They are run before the steps in the "Main Execution" section run. - If these steps fail -> Steps in "Main Execution" are not run but switch to "Tear Down". - If these steps pass -> Steps in "Main Execution" are run. |
| Main Execution | Tab | Show all steps of the test case |
| Tear Down | Tab | Steps are run when the test case (steps in "Main Execution") is executed. |
| Web | Step Package | Including steps used for testing in web app |
| Mobile | Step Package | Including steps used for testing in Mobile app |
| Window | Step Package | Including steps used for testing in Window |
| API | Step Package | Including steps used for API testing |
| Database | Step Package | For interacting with Database |
| Image | Step Package | For steps interacting with Image |
| Core | Step Package | For controlling steps |
| Steps | Column | Represent as a short Test name. This is drag and dropfrom this left hand list. |
| Platform | Column | Represent which platform test scripts will run in |
| Input | Column | Data need to input for the stepAble to use variable with syntax:$.this.variable` |
| Output | Column | Output data of previous step used as a input of nextstepAble to use variable with syntax: $.this.variable |
| Description | Column | Used to describe more detail for a test name. |
2.4.3. Tab(s) in Test cases
2.4.3.1. "Variable" tab
| No | Object | Type | Description |
|---|---|---|---|
| 1 | Input Variable | Including variable(s) which used to bind data in test suite | |
| 2 | Output Variable | When call to keywords which return value and user want to use this value | |
| 3 | Local Variable | Variable used directed in this test case | |
| 4 | Repo’s…variable | When Object having variable and be use in this test case, variable of that Object will be auto-added in this section for user to add var’s value | |
| 6 | Add button | button | To add new variable that you want to create |
2.4.3.2. “Problems” tab
“Problems” Tab includes the information about the errors and warnings contained in the script.
2.4.3.3. "Log" tab
“Log” Tab includes information so that we can understand the real problems you face when using the tool. So, if you get errors/bugs while using the tool, please copy them to us and talk about how you did it.
2.4.3.4. “Recorder” tab
“Recorder” tab displays history of recorded steps of test case, you can able to rename recorded element correctly. The informations in “Recorder” tab display when the recorded test case is executing.
