Invoke and verify is a term unique to CA Application Test and refers to the products ability to test and validate response across all layers of an applications with a single test. This unique ability makes CA Application Test a great fit for organizations that need to test applications that must work with legacy systems, custom applications, ESBs and back-end databases. For example, if we want to check that an order was placed from a Mobile device under test, we may look within an enterprise service or Order Management System to validate the proper order entry - only when these two/three validations are complete can we state that we have validated the functionality.
In CA Application Test, API and non-API tests are created in the same way, using a code-less visual designer, one test can include API and non-API tests. SOAP, REST, general HTTP based APIs, JMS Messaging, Java, and more are supported. Users can model a single test case with steps that invoke and verify an API’s behavior and performance, as well as validate database calls, SOAP messages and many more types of transaction Test can contain a mix of any type of underlying technology step types, across any number of APIs.
- First, Application Test Connects to an object on the application server, or over the Internet.
- Next, Application Test Gathers information about the component, showing you available methods for interacting with it.
- Then, you can Invoke, or the target system with a method, to create a result.
- CA Application Test then gets the Response from that object as a behavior - so you can make a test assertion against that behavior as part of your testing process.
- CA Application Test can then React to that response and invokes the next step in the testing workflow.
Since CA Application Test is an integrated testing suite, the value of Functional Tests continues, and tests are Reused in other processes. For instance, you can save the response data within a database, use that data to validate the behavior of another component or sequence of steps, save that functional test sequence as part of a business workflow, check the workflow in deployment at load, and then monitor its performance within a set of workflows... the list goes on.
To learn how to use the invoke ability in CA Application Test 10.0 visit:
https://docops.ca.com/devtest-solutions/10-0/en/using/using-ca-application-test/using-devtest-workstation-with-ca-application-test/running-test-cases-and-suites/lisa-invoke
To see a quick tour of CA Application Test visit:
https://youtu.be/BAPRlADX8qQ