# Appvance Method ![](https://docs.appvance.net/uploads/images/gallery/2026-07/scaled-1680-/45aoOPt5b8yRLllL-75d8ef9c0f9b.png) 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.[![image.png](https://docs.appvance.net/uploads/images/gallery/2026-08/scaled-1680-/tmfPEckx0gQ6j9cM-image.png)](https://docs.appvance.net/uploads/images/gallery/2026-08/tmfPEckx0gQ6j9cM-image.png) Here is a brief explanation of the terminology used in [The Appvance Test Methodology](/books/scalability-and-performance-test-methodology/page/scalability-and-performance-test-methodology) --- Last updated: August 17, 2026 If you have any feedback on this topic, please contact us at