LISA Validate's New Feature: LISA Workflow Pathfinder
The automation capabilities of LISA's Workflow Pathfinder technology drastically reduce the risk and cost of integration testing, by providing more complete functional and performance test coverage across multiple layers of the application.
How LISA Pathfinder works:
Pathfinder automatically injects LISA test cases into the system under test, then traces the workflow throughout the workflow of the application, utilizing servlet filter APIs, log4j APIs, and standard EJB3 mechanisms to watch transactions as they go into the application server. For instance, a web service is implemented in a EJB running in JBoss application server. The EJB layer provides business logic, and then stores the web service inbound request into a database. So from a testing standpoint, we want to validate the web service interface, verify the business logic, and then validate that the database was updated.
In LISA, testers simply make the call to the web service as you do today. Then Pathfinder will graphically show the EJB that was called, which implements the web service. Then the tester sees the SQL statements that were run against the database. From a testing standpoint, a tester can now see the path a web service takes, without having to read Java code, or relying on documentation and trial-and-error to explore the system. The tester can then invoke the EJBs directly from LISA, if component-level testing is required, and the test can validate results in the database with SQL calls.
Pathfinder not only opens up what is actually happening within the application, but the data and response times for each component called will be shown. This allows a tester to only test at different layers of the application, but allow bottlenecks in the implementing technologies to be seen. For instance, it may not turn out that the web service is the bottleneck, as the Pathfinder test could report that the underlying EJB is eating up 80% of the response time, or that the database update is taking 5 seconds.
From a system documentation standpoint, managers always wonder how much of the system code is actually being tested. Especially at integration time, the idea of full regression testing is often discarded for a late night "install and see if it breaks" test - a very risky level of test coverage for your end customers. Even in strong development shops, functionally aware test coverage for the implementation layers behind the web page or web service is usually not known, even if those components were subjected to thousands of procedural unit tests. LISA visually shows test coverage, so the tester can specifically see that we have tested 20 web pages, the 25 web services feeding them, and that the system services implementing these are 125 EJBs that make 100 SQL calls to the database.
LISA Pathfinder provides exceptional visibility and automation into SOA and integration testing, so that "black box" and "white box" testing are no longer separate disciplines.