Appvance Method

The Appvance Test Methodology uses three key concepts to define and organize tests:

• Use Case – describes the functionality or approach being tested. For example, a test comparing XML parsing techniques could have two use cases: one using the Xerces DOM parser and another using JAXB XML binding.
• Test Case – defines the specific inputs or conditions under which an individual test is executed. For example, when comparing service throughput for different message payload sizes, two test cases could be defined: one using a 500-byte XML document and another using a 10,000-byte XML document.
• Test Scenario – defines the complete execution by combining the required use cases and test cases into a single test.

The Appvance methodology differs from traditional software testing in an important way: it is designed to evaluate not only whether functionality works correctly, but also how the system behaves under different conditions and workloads.

This distinction is particularly important for scalability and performance testing, where the same functionality may need to be evaluated across different payload sizes, concurrency levels, environments, and execution conditions.

Here is a brief explanation of the terminology used in The Appvance Test Methodology

Last updated: October 15, 2026

If you have any feedback on this topic, please contact us at documentation@appvance.ai

Methodology in practice

Apply the Appvance Method by combining representative user goals, reusable test assets, data variation, and measured results. Keep the workload definition, environment, and acceptance criteria stable between comparisons so changes in throughput or response time can be attributed to the system under test.