Skip to content

Test definition

APIJockey TEST is a webservice test application.

Testing web services isn't an easy task:

  • there is no user interface
  • there are implicit business processes around these services that need to be taken into acount
  • data models are based on technical structures, use keys and reference ids. Creating valid requests is time-consuming and verifying responses is even harder.

APIJockey TEST will help you to create requests, assess and verify web services responses and automate this assessment to a certain degree.

APIJockey TEST stores all data in a local database, backed by Apple's Core Data technology.

APIJockey TEST organizes tests in a hirarchy. A test definition describes a test case with its test steps and the assertions defined on the teststeps. That means, a test case can be passed in a test run only, when all teststeps can be run through and all assertions have passed.

Repository

First step in the test definition is the creation of a repository. You can create as many repositories as you want. A Repository contains a structure of test cases AND you can execute the contained testcases.Repositories are intended to support several container types, although APIJockey TEST currently supports one local SQLLite (specifically CoreData© an Apple product) database, only. They help you group your tests and support persisted test executions.

See, how to create a test definition Organize your repostories in the Repository list view

Testset

Once you have created a repository, you start to create Testsets. Testsets contain the actual Testcases. Testsets can be applied for various differenciations like use cases, types of tests (regression tests, new development). Testing includes several tasks, such as:

  • regressions testing
  • test new functionality
  • exploration testing
  • persisted test run executions
  • Testsets will help you to organize large sets of Testcases. Find help to manage your testsets in Testset list view
  • Testsets should not be used to differenciate test environments.
  • Testsets make also sense, when Testcases use common variable data.

Find help to manage your testsets in the Testset list view

Testcase

A testcase

  • represents what you want to test.
  • defines the teststeps, the assertions and validations to test a functionality.
  • can include several endpoints
  • can run with randomized data and capture data from its test steps
  • has run successfully, if all Teststeps have run successfully. There are two types of testcases:
  • A testcase that runs each teststep once.
  • A data based testcase that runs teststeps based on a set of input data for each entry in this data set.

Find help to manage your testcases in Testcase list view You define the actual Testcase on a Testset. You can create an arbitrary number of Testcases on a Testset.

Teststep

APIJockey TEST supports a numbe of teststeps that you can create and arrange however you like and need to A Teststep is a concrete step in you Testcase run. - You run a SOAPTeststep or HTTPTeststep to send a request and receive a response. - You may assert this response. - You may tranfer response information to a variable which in turn is a prerequisite of subsequent teststeps. Each of these teststeps has configuration options, which are described in the section Teststeps

Test run options

You have two different types of test runs availabe:

  1. instant test runs
  2. persisted test executions

Instant test runs

All test runnable elements provide a play button that starts the test run. A result status icon provides visible information of the test result status.

visualization test run results for teststeps

Above: screenshot of the teststep action buttons with test run result icon

Persisted test executions

Test executions are persisted test runs. They can be started from the repository or testset list view and perform basically the same test operations as an instant test run. The difference is that the test execution results are persisted and can be accessed at any point in time. This gives you a great opportunity to get back to previous runs and compare requests and responses.

conceptual testexecution overview

Above: screenshot of the test execution view When you select a test execution, you will see the list of testcase executions and teststeps execution, drilled down to each indivudal Random and Teststep Value Provider output value.