Checklist based testing ISTQB

The common type of software testing is to begin running the software product and make monitoring, with the expectancies that it will be not difficult to differentiate between expected and unexpected conduction.

//qatestlab.com/pressroom/qa-testing-materials/what-is-checklist-based-testing/

0·Kommentier's als erstes:

Checklist-based testing

According to ISTQB, When applying the checklist-based testing technique, the experienced Test Analyst uses a high-level, generalized list of items to be noted, checked, or remembered, or a set of rules or criteria against which a product has to be verified.
These checklists are built based on •     a set of standards •     experience •     and other considerations. A user interface standards checklist employed as the basis for testing an application is an example of a checklist-based test.

Applicability

Checklist-based testing is used most effectively in projects with an experienced test team that is familiar with the software under test or familiar with the area covered by the checklist [e.g., to successfully apply a user interface checklist, the Test Analyst may be familiar with user interface testing but not the specific software under test]. Because checklists are high-level and tend to lack the detailed steps commonly found in test cases and test procedures, the knowledge of the tester is used to fill in the gaps. By removing the detailed steps, checklists are low maintenance and can be applied to multiple similar releases. Checklists can be used for any level of testing. Checklists are also used for regression testing and smoke testing.

Limitations/Difficulties

The high-level nature of the checklists can affect the reproducibility of test results. It is possible that several testers will interpret the checklists differently and will follow different approaches to fulfil the checklist items. This may cause different results, even though the same checklist is used. This can result in wider coverage but reproducibility is sometimes sacrificed. Checklists may also result in over-confidence regarding the level of coverage that is achieved since the actual testing depends on the tester’s judgement. Checklists can be derived from more detailed test cases or lists and tend to grow over time. Maintenance is required to ensure that the checklists are covering the important aspects of the software being tested.

Coverage The coverage is as good as the checklist but, because of the high-level nature of the checklist, the results will vary based on the Test Analyst who executes the checklist.

Types of Defects Typical defects found with this technique include failures resulting from varying the data, the sequence of steps or the general workflow during testing. Using checklists can help keep the testing fresh as new combinations of data and processes are allowed during testing.\

Famous Testing Areas

• This is the complete software testing guide for those who wants to or have started their careers as a software test professional.

• Learn: What is automation testing, why we need it, when we need it, different automation tools etc.

• To become a successful Quality center admin, follow our recent articles on quality center 11

Checklist-based testing is a type of software testing based on the pre-planned “to-do” list of tasks called a checklist. Professional testers, who have sufficient technical experience usually complete these lists. QA [Quality Assurance] engineers use such checklists to guide the testing activities.

Very often different software systems are tested in the same way to see whether it is possible to detect the special defects or manage functional conditions and data without addressing to some systematic technique. Such forms of elementary and informal testing are called ad hoc [random] testing. Checklists are used to structurize this type of testing in order not to waste time repeating the same tests. Such lists can be online, physical or mental.

Commonly used testing checklists

• Functional [black-box] checklists contain checks for dominant functions of the complete system or for the definite functions of the lower levels.
• System elements checklists [white-box] examine sub-systems and modules of higher levels as well as special data items at secondary levels.
• Structure/feature checklists path through various aspects such as the list of customers and producers for definite sources or units sharing some average data, etc.
• Properties checklists test fixed values such as definite specification units, code systems, etc.

QATestLab has a checklist for testing iOS and Android application. Besides, here is the example of usability testing checklist.

Advantages of using checklists in testing

Checklist-based testing is widely used by QA experts advocating for its convenience and productivity. Their knowledge and experience form the base for performance testing of a high quality. Main reasons to use this type of tests are:

1. Flexibility. This kind of checking can be used in all testing types.
2. Easy to create. It is not difficult to create, use and maintain a checklist.
3. Analyzing the results. Checklists are easy to follow and examine.
4. Team integration. The checklist can be ready-made guidance and help new testing personnel to integrate into work.
5. Deadlines control. This type of testing helps to control test accomplishment and not to miss some critical bugs before the deadline.

Difficulties of using checklists in testing

1. Different interpretation. QA engineers with various backgrounds can accomplish identical tasks using different approaches.
2. “Holes” in coverage. It is difficult to capture all functional or structural components, especially those of higher levels.
3. Item overlap. Trying to cover a big scope of material there may be a duplication of the same information. This can lead to excessive testings.
4. Reporting problems. Complex system components, functions, and their interaction are difficult or even impossible to illustrate, applying checklists.

An experience-based test design technique whereby the experienced tester uses a high-level list of items to be noted, checked, or remembered, or a set of rules or criteria against which a product has to be verified.

In simple English:

You have a very high level checklist and you check items off it as you test. 

Field notes:

1. Note that this is not the same as exploratory testing. 

2. The check list is usually the most basic version of a test case.

3. This method relies heavily on the experience of the tester.  

4. The experience of the tester with the system under test is more important than the general test experience of the tester.

5. The checklist does not usually support recording extensive test results.

Page 2

Note: Hi, The latest version of glossary have moved up by a few numbers. The terms and their meaning remain the same. I keep updating these as i get time. if you want some terms early, send me an email.

Click on the words below, to learn and understand them easily.

A

acceptance Criteria *

acceptance testing

accessibility testing

accuracy

accuracy testing

acting [IDEAL]

actor

actual result

ad hoc testing

adaptability

Agile Manifesto

Agile software development

Agile testing

alpha testing

analytical test strategy

analytical testing

analyzability

anomaly

anti-pattern

API

API testing

assessment report

assessor

atomic condition

attack-based testing

attractiveness

audit

audit trail

automated testware

automation code defect density

availability

Availability

Acceptance

Acceptance testing

Availability

Audit

B

C

T

Test Strategy
Testability Review

Test Run

Test Run Log

R
Regression-averse testing

W - Click on the words below, to learn and understand them easily

Walkthrough - F, ATM

WAMMI - ATA

WBS

Website Analysis and MeasureMent Inventory [WAMMI] - ATA

White-box technique

white-box test design technique - F, ATT

white-box testing - F

Wide Band Delphi - ATM

wild pointer - ATT

Work Breakdown Structure