About ISTQB Certification

Q. 1: What is ISTQB?

ISTQB stands for "International Software Testing Qualifications Board". It is Belgium based International body legally established in the year 2002.

Software testing professionals from all over the world joined hands in formulating standardized contents for further education in the field of Software Testing. It is a multiple-choice exam & is an education program offered in 38 countries

ISTQB Website



Q. 2: How many Levels of Certification are provided by ISTQB?

The ISTQB has come out with an International Qualification Scheme called"ISTQB Certified Tester".

Presently there are two levels of exams leading to the specific levels of certification.

1) Foundation Level Certification: Name of this certification is "Certified Tester Foundation Level" (CTFL). This is the only one foundation level exam.This is an entry-level certification meant for people entering the field of testing and for experienced professionals desiring to move up the ladder of ISTQB certifications. 

Foundation Level Certification offers evidence that the certified person has a broad understanding of the key concepts & fundamental best practices of software testing.

2) Advanced Level Certification: This is the intermediate level certification. Name of this certification is "Certified Tester Advanced Level" (CTAL).

Advanced Level Certification offers evidence that the certified person is a committed testing professional and has thorough understanding of key concepts & advanced best practices of software testing.

The prerequisites for applying for the Advanced level exam are as under:

A) For Bachelor’s Degree (or higher) Holders in Computer Science or related fields

1) Must have passed the Foundation Level Exam

2) 24 Months of Testing Experience in IT, Testing, Development, QA, Engineering or related fields (For any 2 sub-levels)

3) Min. 36 Months of experience mandatory for Advanced Level Complete Certification (For all 3 sub-levels)

B) For Non Bachelor ’s Degree (or higher) Holders in Computer Science or related fields

1) Must have passed the Foundation Level Exam

2) 60 Months of Testing Experience in IT, Testing, Development, QA, Engineering or related fields

Sub Levels of Advanced Level certifications: The Advanced Level certification exam has following three inter-related sublevels. Candidate can go in for either or all of these advanced level certifications.

Sub Level -1: Technical Test Analyst

Sub Level -2: Test Analyst

Sub Level -3: Test Manager

Key Features of the 3 - Advanced Sublevel exams

a) A single syllabus exists for all the three sublevels.

b) There is a separate paper for every sub-level and every exam is of 180 Minutes Duration.

c) Sub-Levels can be taken up in any order.

d) An individual Certificate is granted on successful completion of every sublevel exam.

Additional Advanced Level Certification: After completing the above three advanced level certifications, one can go in for an additional Advanced Level Certification by the name "Advanced Level (CTAL) – Full Advanced Level". This is an exam of 1.5 hours duration.

3) Expert Level Certification: Has not started yet. Expert Level Certification is meant for leaders of the field of software testing with eight or more years of experience.

Expert Level Certification offers evidence that the certified person is a seasoned testing professional and has consistent understanding & execution of proven cutting edge techniques in testing.

Q. 3: Who provides the ISTQB Certification?

Almost all-major countries are the member of the parent body i.e. ISTQB. These member countries have their local Software Testing Qualification Boards. These local boards provide their inputs to the syllabus and question papers for various exams including the process of examination.

Such boards conduct the exams strictly in accordance with the common syllabus defined by ISTQB & provide necessary certification.

In India, ITB (Indian Testing Board) is the ISTQB approved national board & provides the "ISTQB Certified Tester" Certification in India.

ITB (Indian Testing Board) Website

Q. 4: What is the period of validity of ISTQB Certifications?

 

1) ISTQB Certified Tester - Foundation Level Certificate (CTFL): Valid for whole Life.

2) ISTQB Certified Tester - Advanced Level Certificate (CTAL): Valid for whole Life.

Q. 5: What are the Advantages of ISTQB Certifications?

1) It is a known fact that the common practices generally lag behind the best practices by around 25 - 30 years. Basic advantage of ISTQB certifications is that these are aimed at bringing the common practices to the level of best practices.

2) ISTQB certifications are of International nature, whose certificate is recognized in several countries across various continents.

3) Since the syllabus of ISTQB certification exams is targeted to various concepts & techniques having real-world application, the ISTQB certification carries respect of the highest order among the International community.

4) ISTQB certification means an automatic certificate of sound practical knowledge & high caliber of the certified professional. This is certainly regarded as a golden feather in the cap of the certified person.

5) Due to great respect commanded by the ISTQB certification in the trade, it helps the aspirants in shaping their career path.

6) ISTQB certification provides a rock solid foundation for professional growth to the certified person.

7) ISTQB delivers value to the software testing profession itself.

Q. 6: What are the Salient Features of the Foundation Level (CTFL) Exam?

1) It is a Knowledge Based Exam. 

2) The aspirant need not have any prior experience.

3) No re-certification is required after some time, since the certificate remains valid for the whole life.

4) The Syllabus is very well structured & easy to understand.

5) This certification signifies that the:

a) Aspirant is committed to the software testing as a profession

b) Aspirant is very well conversant with various concepts and terminology of testing.

c) Aspirant is able to use the specialized techniques like code coverage analysis, boundary values analysis & Equivalence partitioning etc.

Q. 7: What is the Structure of Foundation Level Exam conducted by ITB?

This exam is designed to evaluate the aspirant’s knowledge & understanding of the entire syllabus of Foundation level exam.

All ISTQB Foundation exams use the same format with following features:

1) This is a Closed Book Exam – Requiring you to darken the appropriate circle with the help of a pencil.

2) Exam consists of 40 multiple-choice questions each carrying 1 point for the correct answer (Total 40 Points)

3) Each question presents 4 or 5 possible answers, out of which only one is the correct one.

4) Time allowed for finishing the test: 75 Minutes

5) Passing Score: More than 65% (Minimum 26 Points are required to pass)

6) There is no negative marking.

7) %age breakup of questions in the exam:

a) 50% Questions – K1 Level (To check basic knowledge & remembering ability of a concept)

b) 30% Questions – K2 Level (To check the ability to compare, classify & summarize)

c) 20% Questions – K3 Level (To check the ability to analyze, apply the knowledge. Can include Numericals as well)

Explanation of various Knowledge Levels or K-Levels

8) Tentative Breakup of Syllabus for Foundation Level Certification (CTFL).

a) The syllabus covers following six major topics & the following table indicates the number of questions expected in the exam.

No.	Chapter	Topics covered	No. of Questions Expected in the Exam
1.	The principles of testing	Terminology; why testing is necessary; fundamental test process; psychology of testing; re-testing and regression testing; expected results; prioritization.	7
2.	Testing throughout the lifecycle	Models for testing; economics of testing; high level test planning; acceptance testing; integration testing in the large; functional and non-functional system testing; integration testing in the small; component testing; maintenance testing.	6
3.	Static testing techniques	Reviews and the test process; types of review; static analysis.	3
4.	Test design techniques	Dynamic testing techniques, (Behavioral) Black-box and (structural) White-box testing techniques; error guessing, BVA etc.	12
5.	Test management	Organization; configuration management; test estimation, monitoring and control; incident management; standards for testing.	8
6.	Tool support for testing	Types of CAST tool (Computer-Aided Software Testing); tool selection and implementation.	4
		Total No. of Questions	40

b) The following table indicates the chapter wise breakup of questions according to different knowledge levels 

No.	Chapter	K1	K2	K3	Total No. of Questions Expected in the Exam
1.	The principles of testing	4	3	0	7
2.	Testing throughout the lifecycle	4	2	0	6
3.	Static testing techniques	2	1	0	3
4.	Test design techniques	4	2	6	12
5.	Test management	3	3	2	8
6.	Tool support for testing	3	1	0	4
	Total	20	12	8	40

9) Format of questions: In All ISTQB Foundation exams questions are presented in two standard formats like:

1) Basic Format: Every question consists of a stem that includes the real question & offers four response options out of which one & only one is the best & the correct choice. Options other than the correct one are known as distracters. It is possible that a particular distracter statement may also be true otherwise, but is treated as incorrect response simply because it doesn’t qualify to be the best choice, when associated with the present question.

A sample question with explanation of related terms is as under.

Sample Question 1: Which of the following is a MAJOR task of test planning?

A. Scheduling test analysis and design tasks.
B. Initiating corrective actions.
C. Monitoring progress and test coverage.
D. Measuring and analyzing results.

Explanation: Here the stem portion of the question is "Which of the following is a MAJOR task of test planning?". Generally in some questions an extra emphasis is laid on some particular word, for example in this sample question –MAJOR. This type of emphasized word can appear in the form of All capitals, or can be simply Bold, or can be written in Italics. Likewise common words that are used in the exam for providing more emphasis are: MAJOR, USUALLY, KEY, MORE, LEAST, MAIN, MOST, OFTEN, OPTIONALLY, MOST LIKELY, MUST

2) Roman Format: In the roman format type questions the stem of the question consists of many statements. Four types of response options & choices of likely answers depend upon the best combination of statements.

Roman format questions are further divided into two parts like

a) Roman simple format: A sample of roman simple format question with explanation of related terms is as under.

Sample Question 2: Some tools are geared more for developer use. For the 5 tools listed, which statement BEST details those for developers

I. Performance testing tools.
II. Coverage measurement tools.
III. Test comparators.
IV. Dynamic analysis tools.
V. Incident management tools.

A. i, iii. and iv. are more for developers.
B. ii. and iv. are more for developers.
C. ii, iii. and iv. are more for developers.
D. ii. and iii. are more for developers.

Explanation: Here the stem of the question consists of five statements marked as I, II, III, IV & V. In exam you can find these statements marked in roman small numerals like I, ii, iii, iv, v or alphabetically it can be S,T,U, V etc.) or something quite similar. The stem may have 2, 3, 4 or 5 statements as per the need. It may be noted that all these stem statements may be true in their own sense; however the correct answer shall be the one which completely describes the correctness of the combination of statements.

b) Roman typical format: It is slightly more difficult variant of roman type questions of K2 or K3 levels. A sample of roman typical format question with explanation of related terms is as under. K3 type questions sometimes contains some figures, flow charts, or small piece of codes that are included in the stem part.

Sample Question 3: Match the following terms and statements.

1.Decision Table Testing
2.Decision Testing
3.State Transition Testing
4.Exploratory Testing

W. Testing carried out w boxes to achieve specific test objectives, possibly to complement structured testing.

X. A test technique used which may be used to verify different system re depending on current conditions or previous history.

Y. A test technique which combines combinations of inputs that might not otherwise have been exercised during testing.

Z. A form of control flow testing based on decision outcomes.

Options:
A. 1Y, 2Z, 3X, 4W.
B. 1X ,2W, 3Z, 4Y.
C. 1Z, 2X, 3W, 4Y.
D. 1Z, 2Y, 3X, 4W.

Explanation: Here the stem of the question consists of two sets of statements marked as 1,2,3,4 & second set W,X,Y,Z. For arriving at the correct answer, first set of statements need to be carefully matched with the second set of statements.

Q. 8: What is the Syllabus for various ISTQB certifications Exams?

Download the syllabus from the following links:

1) ISTQB Foundation Level (CTFL) Syllabus - 2011

2) ISTQB Advanced Level (CTAL) Syllabus - 2007

The Advanced Level syllabus is divided into three areas like:

a) Advanced behavioral testing or Black Box testing & testing standards for business oriented testing professionals.

b) Test automation and advanced structural testing or White Box testing for programmers & software testers.

c) Sophisticated test management concepts for Professional Managers. 

The Advanced Level syllabus covers following topics: 

a) Basic Aspects of Software Testing
b) Testing Processes
c) Test Management
d) Test Techniques
e) Testing of Software Characteristics
f) Reviews
g) Incident Management
h) Standards & Test Improvement Process
j) Test Tools & Automation
k) People Skills - Team Composition

ISTQB Foundation Practice Tests

ISTQB Foundation Practice Test  1

ISTQB Foundation Practice Test  2

ISTQB Foundation Practice Test  3

ISTQB Foundation Practice Test  4

ISTQB Foundation Practice Test  5

ISTQB Foundation Practice Test  6

ISTQB Foundation Practice Test  7

Benefits of Documentation in Software Testing

Documenting the testing process not only gives a tester an overview of the product, but it also saves time, effort as well as money. Documentation is an important component of the software testing process and it provides a systematic approach to testing as well as a proper information about the product as testers shouldn’t rely only on verbal communication. It can either be from a customer’s point of view or that of the client.

Documentation consists of the requirements, test plan, test strategy and walkthrough.

A write up on bloggerspath.com highlights some benefits of documentation and how it can add up to an organization’s long term goals.

1.    Removes Uncertainties
The main reason behind documentation is to either reduce or remove any uncertainties with regards to the product. It also removes the confusion that often arises when it comes to the allocation of tasks.

2.    Offer good training material to fresher’s
Documentation not only provides a systematic approach to software testing, but also offers good training material to freshers in the software testing space. Rather than using tactics to learn how to implement the process, software testers can learn by using the material.

3.    Good Marketing Strategy
Documentation in software testing can also be a good marketing as well as a good sales strategy to display ones preference towards maintaining a good process.

4.    Good Coverage and Estimating the Project’s Deadline
Documentation can not only offer the testing teams a good coverage of the product but also lets them determine the deadline as well as the scope of the project.

It should always be remembered that QA projects that have all the required documents have a high level of maturity.

Although, with the various benefits of documentation and the availability of documentation templates on the internet, many companies are giving little importance to documentation.

5 Popular Open Source Test Management Tools

1.    Jite
The Jite test management tool from Prisma SW Solutions allows testers to write as well as run tests for any application or devices before releasing it. Some of its features include:
a.    Project Management
b.    Management divisions
c.    Creating and updating of test
d.    Defining the level of a test
e.    Mapping the links between test and functions
f.    Integration with Jira and others

2.    qaManager
The qaManager tool is platform independent and with its easy to install procedures, it allows QA professionals to manage projects effectively. Some of its important features include:
a.    Tracking Engineering Releases
b.    Tracking QA/Customer Releases
c.    Keep a Track of Testing Cycles
d.    Online test case management
e.    Manage and Track Resource Allocations
f.    Maintain resource and customer details and others

3.    QaTraq Professional
This tool not only helps QA professionals to increase their productivity but also to increase the visibility of the progress of the test and this in turn improves the quality of the application. Thus, making it one of the leading test case management tools available today.

4.    Tesly
The Tesly test management tool allows QA mangers to track the progress of the testing process. This is possible as testers use a common interface to report completion of test cases. Some of its features include creation and edition of test plans, executing test plans, results tracking and others.

5.    XQual Studio
The XQual Studio can handle the entire testing lifecycle from users’ requirement to test reports and test campaigns. It is also a powerful yet an easy-to-use bug-tracking database. The tool supports automated as well as manual test executions.

Mobile Testing with (UFT) QTP 11.5

HP recently announced its official mobile test automation solution –UFT Mobile – jointly developed by HP and Perfecto Mobile. This solution allows users to naturally extend their existing HP Functional Testing and Application Lifecycle Management environment to mobile applications.

To address key challenges in testing mobile applications across multiple devices in a highly fragmented market, UFT Mobile leverages two specially designed capabilities with respect to object recognition and analysis. These features are known as Hybrid Object Support and Hybrid Test Automation (for closed operating systems like iOS).

Hybrid Object Support in HP UFT Mobile

UFT Mobile utilizes a hybrid approach to object recognition, combining the use of visual object analysis and object level analysis. Such an approach enables users to choose the most appropriate object recognition technique for a given script, based on the application’s complexity and various testing scenarios, without compromising quality.

While each approach has its advantages and drawbacks, both are essential in mobile test automation and completely supported in UFT Mobile. Visual screen analysis uses OCR and advanced image matching technologies to replicate the REAL user experience on the actual device. Object level analysis enables fast and 100% accurate test automation, based on access to the low level OS.

Using only object level analysis, users may miss GUI defects, object truncations and so forth. On the other hand, relying solely on Visual Objects, you may not always being able to identify the correct objects from the application under test (see the example below).

Hybrid Test Automation in HP UFT Mobile

UFT Mobile supports automated testing of mobile applications on any OS platform (e.g., Android, iOS, BlackBerry and others). Patented technology allows users to develop device-agnostic scripts across mobile operating systems and devices. The screenshot below shows how UFT Mobile can be used to test a mobile application on two devices, each using a different mobile operating system. (Click on the image for full view)

When developing automated tests on the closed iOS operating system, test developers are limited by their inability to access to the low level OS objects, and are not able to identify the unique objects and perform actions on them. To overcome this limitation, UFT Mobile supports two different methods for iOS test automation: jailbreaking and source instrumentation. UFT Mobile uses a hybrid approach that lets you choose which type of tests to implement on which iOS device according to the nature of your application, project needs, and policy.

Let’s take a look at these methods.

• Jailbreaking: This refers to the process of removing the limitations placed by Apple on the iOS device in order to get low level (root) access to the operating system. This allows the tester to be able to recognize the objects within the application being tested. It is important to understand that jailbreaking has no impact whatsoever on the source code, functionality or security of the application under test. Keep in mind that this testing method is carried out in a closed and secure environment that is used only for testing purposes. After testing, the application will run on a standard iOS device and undergo the Apple certification process.
• Source Instrumentation: Source instrumentation is performed by compiling the application being tested with an additional piece of code that provides access (“back door”) to the low level OS for object recognition. This code enables the tester to execute the low level calls and get the Object IDs from the operating system (without the need to root/jailbreak the device).

What’s important here is the need to be able to support both methods within a single solution. UFT Mobile provides this flexibility, enabling organization to optimize their test automation to meet the needs of increasingly complex mobile applications.

Bottom Line

HP UFT Mobile enables testers/developers to test their application on any device or OS through a secure, cloud-based platform. UFT Mobile utilizes an innovative hybrid approach for object recognition, as well as specific hybrid test automation capabilities for iOS, which offer enterprises maximum flexibility, coverage and efficiency in their mobile testing. Check the video below for a quick demo.

5 Tips to Choose the Best Automated Mobile Testing Tool

Bangalore: Mobile applications have revolutionized our lives. Today, with the touch of an option, we can access any amount of information such as getting directions to a restaurant, booking our flight tickets or even order a cab service. The shift from the more traditional desktops to smartphones has resulted in an increase in the demand for mobile applications.

However; the number of smartphones having different features and specifications are increasing daily and this poses many challenges to the testers. Brian MacKenzie in a blog post on northwaysolutions.com highlighted some tips to help mobile app testers choose the best automation tools to test applications.

1) Reusable Scripts
Testers should ensure that the test scripts can be reused across the various devices running the same operating systems irrespective of the version. There are various solutions in the market today that claim to meet this requirement, however the reality is many of them don’t although they come with tag lines such as “object based scripting” and “cross OS scripting”. 

2) Support Emulators/Simulators and other Physical Devices
Testers should be able to run and record scripts across physical devices as well as simulators and emulators.

3) Web Application Support
Hybrid apps, web based apps and native apps have their own advantages and disadvantages not only to the developer but also to the testers and users. Hybrid and Web Based apps are becoming popular and they are likely to replace native apps. Before selecting the tool, the tester should ensure that it support all types of apps.

4) Interruptions Shouldn’t Cause the Test to Fail
Common interruptions such as phone calls and messages shouldn’t cause the test to fail. Testers should ensure that the tool doesn’t get affected by the various interruptions and it should be able to resume once the interruption is over.

5) Integration with Performance Testing Tools
As poor application performance can affect the revenue, testers should ensure that the solution they plan to select can be integrated with other performance testing tool. Furthermore, the solution should be able to measure the performance of the RAM, disk, the battery and the CPU.