A Test Automation Language Framework for Behavioral Models The paper outlines a

Question

A Test Automation Language Framework for Behavioral Models

The paper outlines a language framework to automate the creation of mappings from abstract model-based tests to concrete executable tests when testers have only behavioral models which is done using a test automation language STAL (Structured Test Automation Language). The paper represents that basically STAL is use by testers to dene mappings between elements in the abstract tests to specic sequences of code that will be part of the concrete executable tests. Further, the test automation language can be used whenever abstract tests include the same elements many times, resulting in duplicate components of concrete tests. The paper basically explains STAL in terms of using graph-based test criteria dened on graphs that were derived from state machine diagrams, but it can also be used with other behavioral models and other techniques for designing model-based tests. Secondly, the paper shows the development of a test automation language framework, STALE (Structured Test Automation Language framework), which implements STAL. It utilizes graph transformation to preserve the actual behavior of the language framework. It represents that the testers can use STALE to accept models, programs, and mappings and then automatically generates the fully executable concrete tests. It addresses three key issues for developing the main framework STALE: (1) In first issue it creates mappings and generates test values, (2) second issue includes transformation of graphs and usage of coverage criteria to generate test paths, and (3) final issue solves constraints and generates concrete tests.

Whart are the Strength, Flaws and/or future Work of this article?

Explanation / Answer

Strengths for Stal: Reliable: Tests perform precisely the same operations each time they are run, thereby eliminating human error Repeatable: You can test how the software reacts under repeated execution of the same operation. Programmable: You can agenda complicated tests that bring out hidden information from the application. Comprehensive: You can build a suite of tests that covers every feature in your application. Reusable: You be able to reuse test on dissimilar versions of an request, even if the users border change. Better Quality Software: since you can run more tests in less time with fewer resources Fast: Automated Tools run tests considerably faster than human users. Cost Reduction: As the number of resources for regression test are reduced Flaws: Testing coverage limitation requires more efforts and expenditure during the preparations of test executions. Expensive as one has to spend both time and money to perform white box testing. Every possibility that few lines of code are missed by chance. In-depth knowledge about the programming language is essential to perform white box testing.

Related Questions

Navigate

• Browse (All)
• Browse A
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.