by Nataliia Vasylyna | May 8, 2014 10:00 am
Many experts in software testing find that lightweight guidance is often more beneficial than the detailed one for mobile application testing, desktop testing and web site testing. Such guidance is especially suitable for mobile software products.
Among convenient and useful lightweight types of guidance are checklists and coverage maps. They both are elaborated basing on coverage models and thinking instrument. A test guidance makes testing works specific, measurable and finite.
One can test a mobile application forever basing only on a coverage model or a thinking tool.
A software testing company will confirm that checklists and coverage maps are equally efficient. Some testers prefer one type of test guidance, some prefer another. The thing is that people are different; they favour different ways of representing and acquiring information.
Coverage maps can be created in a special application, printed or drawn on paper. Such map may be worked out for each aspect of the software under test, for each testing type. On the maps testers can indicate what areas, aspects and functions have already been checked, what await checking. It is convenient to do so in course of mobile testing, desktop testing or web site testing.
Source URL: https://blog.qatestlab.com/2014/05/08/what-is-the-difference-between-a-checklist-and-a-coverage-map/
Copyright ©2024 QATestLab Blog unless otherwise noted.