"A test case in software engineering is a set of conditions or variables under which a tester will determine whether an application or software system meets specifications. The mechanism for determining whether a software program or system has passed or failed such a test is known as a test oracle. In some settings an oracle could be a requirement or use case. It may take many test cases to determine that a software program or system is functioning correctly. Test cases are often referred to as test scripts, particularly when written. Written test cases are usually collected into test suites." -- Wikipedia
Besides a description of the functionality to be tested, and the preparation required to ensure that the test can be conducted, the most time consuming part in the test case is the test scripts. Writer, BA or QA engineer has to spend tons of time to list out the detail of input, expected output, precondition and postcondition. Knowledge transformation is also hard if there are many members involved in this test cycle. Reading test script is time consuming, communication is expensive, the misunderstanding could happen everywhere. How can we simplify the process of writing test script, modifying the test script to sync the change of the requirements and design, and improve the quality of QA? Nowadays, many companies are using screen capture or screen recorder software to generate a video as the primary part of test scripts. This will reduce the misunderstanding, shorten QA cycle and improve the productivity.
Well, after having all those test script video how could you manage them? Have a nice try on the video management feature on PrimeObjects.com Information Management System .
No comments:
Post a Comment