Explore topic-wise InterviewSolutions in .

1. TEST planning and control
2. Test analysis and design
3. Test implementation and execution
4. Evaluating EXIT CRITERIA and REPORTING
5. Test CLOSURE activities
6. Read more on fundamental test process

1. Testing shows presence of defects
2. EXHAUSTIVE testing is impossible
3. Early testing
4. DEFECT clustering
5. Pesticide paradox
6. Testing is CONTEXT dependent
7. Read more on seven principles of testing

Testing is necessary in order to identify any defects that are present in software which can cause HARM. WITHOUT proper testing, we could potentially release a software which could malfunction and cause serious injuries.

Examples can be:

• Software in a LIFE support machine which can cause serious harm to a patient;
• Software in a nuclear plant which monitors nuclear activity can cause harm to the ENVIRONMENT
• Banking or financial application which calculates exchange rates can cause financial LOSS to a business

Testing is necessary in order to identify any defects that are present in software which can cause harm. Without proper testing, we could potentially release a software which could malfunction and cause serious injuries.

Examples can be:

• It is a KNOWLEDGE Based Exam.
• The aspirant need not have any PRIOR experience.
• No re-certification is required after some time, since the certificate remains valid for the WHOLE life.
• The Syllabus is very well structured & EASY to understand.

This certification signifies that the:

1. Aspirant is committed to the software testing as a profession
2. Aspirant is very well conversant with various concepts and terminology of testing.
3. Aspirant is able to use the specialized techniques LIKE code coverage analysis, boundary values analysis & Equivalence partitioning etc.

This certification signifies that the:

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.

Miscommunication or no communication:

Quite often, the requirements from the business is not communicated to the development team. Product OWNERS have an idea of what the feature should look like and how it should behave, but if not communicated properly to developers and testers, the finished product might not be as expected. The requirements should be communicated clearly to all stakeholders so everyone has the same understanding.

Software complexity:

The complexity of current software APPLICATIONS can be difficult to comprehend for anyone without experience in modern-day software development. Multi-tiered applications, client-server and distributed applications, data communications, enormous relational databases, and SHEER size of applications have all contributed to the exponential growth in software/system complexity. programming errors – programmers, like anyone else, can make mistakes.

Changing requirements:

The end-user may not understand the effects of changes, or may understand and request them anyway – redesign, rescheduling of engineers, effects on other projects, WORK already completed that may have to be redone or thrown out, hardware requirements that may be affected, etc.

If there are many minor changes or any major changes, known and unknown dependencies among parts of the project are likely to interact and cause problems, and the complexity of coordinating changes may result in errors. Enthusiasm of engineering staff may be affected.

In some fast-changing business environments, continuously modified requirements may be a fact of life. In this case, management must understand the resulting risks, and QA and test engineers must adapt and plan for continuous extensive testing to keep the inevitable bugs from running out of control.

Poorly documented code:

It’s tough to maintain and modify code that is badly written or poorly documented; the result is bugs. In many organizations management provides no incentive for programmers to document their code or write clear, understandable, maintainable code. In fact, it’s usually the OPPOSITE: they get points mostly for quickly turning out code, and there’s job security if nobody else can understand it (‘if it was hard to write, it should be hard to read’).

 Software development tools:

Visual tools, class libraries, compilers, scripting tools, etc. often introduce their own bugs or are poorly documented, resulting in added bugs.

Miscommunication or no communication:

Quite often, the requirements from the business is not communicated to the development team. Product owners have an idea of what the feature should look like and how it should behave, but if not communicated properly to developers and testers, the finished product might not be as expected. The requirements should be communicated clearly to all stakeholders so everyone has the same understanding.

Software complexity:

The complexity of current software applications can be difficult to comprehend for anyone without experience in modern-day software development. Multi-tiered applications, client-server and distributed applications, data communications, enormous relational databases, and sheer size of applications have all contributed to the exponential growth in software/system complexity. programming errors – programmers, like anyone else, can make mistakes.

Changing requirements:

The end-user may not understand the effects of changes, or may understand and request them anyway – redesign, rescheduling of engineers, effects on other projects, work already completed that may have to be redone or thrown out, hardware requirements that may be affected, etc.

If there are many minor changes or any major changes, known and unknown dependencies among parts of the project are likely to interact and cause problems, and the complexity of coordinating changes may result in errors. Enthusiasm of engineering staff may be affected.

In some fast-changing business environments, continuously modified requirements may be a fact of life. In this case, management must understand the resulting risks, and QA and test engineers must adapt and plan for continuous extensive testing to keep the inevitable bugs from running out of control.

Poorly documented code:

It’s tough to maintain and modify code that is badly written or poorly documented; the result is bugs. In many organizations management provides no incentive for programmers to document their code or write clear, understandable, maintainable code. In fact, it’s usually the opposite: they get points mostly for quickly turning out code, and there’s job security if nobody else can understand it (‘if it was hard to write, it should be hard to read’).

 Software development tools:

Visual tools, class libraries, compilers, scripting tools, etc. often introduce their own bugs or are poorly documented, resulting in added bugs.

The main purpose of a Test Technique is to help identify DEFECTS and reduce large number of combinations. Testing everything is not possible, because there are large number of test cases that can be executed against a GIVEN application.

Test techniques such as equivalence PARTITIONING and pairwise testing reduce PERMUTATIONS, while boundary value analysis help to identify defects at boundaries.

The main purpose of a Test Technique is to help identify defects and reduce large number of combinations. Testing everything is not possible, because there are large number of test cases that can be executed against a given application.

Test techniques such as equivalence partitioning and pairwise testing reduce permutations, while boundary value analysis help to identify defects at boundaries.

Software Testing can be divided into two parts:

Black box testing which is high level and does not take into account the internal workings of the software, i.e. the tester doesn’t need to know how each individual components INTERACT with each other.

White box testing which TESTS at very LOW levels, e.g. functions within a class or COMPONENT integration. System Testing is an example of a Black Box Testing, and Unit Testing is an example of white box testing.

Software Testing can be divided into two parts:

Black box testing which is high level and does not take into account the internal workings of the software, i.e. the tester doesn’t need to know how each individual components interact with each other.

White box testing which tests at very low levels, e.g. functions within a class or component integration. System Testing is an example of a Black Box Testing, and Unit Testing is an example of white box testing.

1. BRIEF summary of the defect
2. Full description of the defect INCLUDING steps to reproduce
3. Screenshot attachments if required
4. Date the defect was found and raised
5. Who REPORTED the defect
6. SEVERITY and/or Priority of the defect
7. Which component is the defect assigned

1. DETERMINING the scope and objectives of testing
2. Defining the overall approach of testing, defining entry and exit criteria
3. Making decisions about what to test and who will test which part of the application
4. SCHEDULING test design sessions
5. Assigning resources for DIFFERENT testing activities
6. Deciding which TOOLS to use for testing
7. REPORTING on the progress of testing
8. Producing exit reports

1. EQUIVALENCE Partitioning
2. Boundary Value Analysis
3. Decision Table Testing
4. STATE TRANSITION Testing
5. USE Case Testing

1. COMPONENT TESTING
2. INTEGRATION Testing
3. SYSTEM Testing
4. ACCEPTANCE Testing

An error is a human action PRODUCING an incorrect result.

The error is the activity undertaken by an analyst, designer, developer, or tester whose outcome is a fault in the DELIVERABLE being produced.

When programmers make ERRORS, they introduce faults to program code. We USUALLY think of programmers when we mention errors, but any person INVOLVED in the development activities can make the error, which injects a fault into a deliverable.

An error is a human action producing an incorrect result.

The error is the activity undertaken by an analyst, designer, developer, or tester whose outcome is a fault in the deliverable being produced.

When programmers make errors, they introduce faults to program code. We usually think of programmers when we mention errors, but any person involved in the development activities can make the error, which injects a fault into a deliverable.

Software Testing is necessary because the existence of faults in software is inevitable. BEYOND fault-detection, the modern VIEW of testing holds that fault-prevention (e.g. EARLY fault detection/removal from requirements, designs ETC. through static tests) is at least as IMPORTANT as detecting faults in software by executing dynamic tests.

Software Testing is necessary because the existence of faults in software is inevitable. Beyond fault-detection, the modern view of testing holds that fault-prevention (e.g. early fault detection/removal from requirements, designs etc. through static tests) is at least as important as detecting faults in software by executing dynamic tests.

Error and Mistake are the same thing. Bug, DEFECT and Fault are the same thing.

In general, a human being can make a mistake (error) which produces a defect (bug, fault) in a SOFTWARE application which may cause a failure.

Defects occur because human beings are PRONE to make mistakes, also a software application can be very complex so the integration of different components can cause odd behaviours.

Error and Mistake are the same thing. Bug, Defect and Fault are the same thing.

In general, a human being can make a mistake (error) which produces a defect (bug, fault) in a software application which may cause a failure.

Defects occur because human beings are prone to make mistakes, also a software application can be very complex so the integration of different components can cause odd behaviours.

There is no DEFINITIVE answer to this question. Testing is not absolute and has no limits. However, we can use risk metrics (risk based testing) to IDENTIFY the likely scenarios that can cause the most harm or the sections of the software that is mostly used so that we focus our time and effort to the sections that are most IMPORTANT.

Testing should provide enough information about the status or health of an application, so the STAKEHOLDERS can make INFORMED decision on whether to release the software or spend more time on testing.

There is no definitive answer to this question. Testing is not absolute and has no limits. However, we can use risk metrics (risk based testing) to identify the likely scenarios that can cause the most harm or the sections of the software that is mostly used so that we focus our time and effort to the sections that are most important.

Testing should provide enough information about the status or health of an application, so the stakeholders can make informed decision on whether to release the software or spend more time on testing.

Two types of testing which are very important for testing web APPLICATIONS are Performance Testing and SECURITY Testing. The difference between a web application and desktop application, is that web applications are open to the world, with potentially many USERS accessing the application simultaneously at various times, so load testing and STRESS testing are important.

Web applications are also vulnerable to all forms of attacks, mostly DDOS, so security testing is also very important to consider when testing web applications.

Two types of testing which are very important for testing web applications are Performance Testing and Security Testing. The difference between a web application and desktop application, is that web applications are open to the world, with potentially many users accessing the application simultaneously at various times, so load testing and stress testing are important.

Web applications are also vulnerable to all forms of attacks, mostly DDOS, so security testing is also very important to consider when testing web applications.

1. Sign in with valid login, CLOSE BROWSER and reopen and see whether you are still logged in or not.
2. Session management is IMPORTANT – how do we keep track of logged in users, is it VIA cookies or web sessions?
3. Sign in, then logout and then go back to the login page to see if you are truly logged out.
4. Login, then go back to the same page, do you see the login screen again?
5. Sign in from one browser, then open another browser to see if you need to sign in again?
6. Login, CHANGE password, and then logout, then see if you can login again with the old password.

TEST Techniques are primarily used for two purposes:

a) To help identify defects,
b) To reduce the number of test cases.

1. EQUIVALENCE partitioning is MAINLY used to reduce number of test cases by identifying different SETS of data that are not the same and only executing one test from each SET of data
2. Boundary Value Analysis is used to check the behaviour of the system at the boundaries of allowed data.
3. State Transition Testing is used to validate allowed and disallowed states and transitions from one state to another by various input data
4. Pair-wise or All Pairs Testing is a very powerful test technique and is mainly used to reduce the number of test cases while increasing the coverage of feature combinations.

Test Techniques are primarily used for two purposes:

a) To help identify defects,
b) To reduce the number of test cases.

The DEFINITION of Exploratory Testing is “simultaneous test design and execution” against an APPLICATION. This means that the tester uses her domain knowledge and testing experience to predict where and under what conditions the system might behave unexpectedly. As the tester STARTS exploring the system, new test design ideas are thought of on the fly and executed against the software under test.

On an exploratory testing session, the tester executes a chain of actions against the system, each action depends on the result of the previous action, hence the outcome of the result of the actions could influence what the tester does NEXT, therefore the test sessions are not identical.

This is in contrast to Scripted Testing where tests are designed beforehand using the requirements or design documents, usually before the system is ready and execute those exact same steps against the system in another time.

Exploratory Testing is usually performed as the product is evolving (agile) or as a final check before the software is released. It is a complementary ACTIVITY to automated regression testing.

The definition of Exploratory Testing is “simultaneous test design and execution” against an application. This means that the tester uses her domain knowledge and testing experience to predict where and under what conditions the system might behave unexpectedly. As the tester starts exploring the system, new test design ideas are thought of on the fly and executed against the software under test.

On an exploratory testing session, the tester executes a chain of actions against the system, each action depends on the result of the previous action, hence the outcome of the result of the actions could influence what the tester does next, therefore the test sessions are not identical.

This is in contrast to Scripted Testing where tests are designed beforehand using the requirements or design documents, usually before the system is ready and execute those exact same steps against the system in another time.

Exploratory Testing is usually performed as the product is evolving (agile) or as a final check before the software is released. It is a complementary activity to automated regression testing.

1) ISTQB CERTIFIED Tester – Foundation LEVEL Certificate (CTFL): Valid for whole Life.

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

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

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

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.

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.

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 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.