4 avg. rating (80% score) - 5879 votes
Are you looking for a job change? Are you prepared in attending an interview? Are you worried for job interview preparation? Then do not worry, we’ve a right answer for your job interview preparation. If you are preparing for ISTQB job interview and don’t know how to crack interview and what level or difficulty of questions to be asked in job interviews then go through Wisdomjobs ISTQB interview questions and answers page to crack your job interview. ISTQB is the International Software Testing Qualifications Board which conducts the exams on testing technology and provides certification if the candidates pass the exam. This certificate is accepted globally. Below are the frequently asked ISTQB interview questions and answers which makes you comfortable to face the interviews:
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.
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.
1) ISTQB Certified Tester – Foundation Level Certificate (CTFL): Valid for whole Life.
2) ISTQB Certified Tester – Advanced Level Certificate (CTAL): Valid for whole Life.
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.
Test Techniques are primarily used for two purposes:
a) To help identify defects,
b) To reduce the number of test cases.
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.
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.
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.
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.
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 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.
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.
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.
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.
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.
This certification signifies that the:
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:
ISTQB Related Tutorials
|QTP Tutorial||Quality Management Tutorial|
|Database Testing Tutorial||CoffeeScript Tutorial|
|Software testing Tutorial||Software Development Lifecycle (SDLC) Tutorial|
|QUnit Testing Tutorial|
ISTQB Related Interview Questions
|QTP Interview Questions||Manual Testing Interview Questions|
|Quality Management Interview Questions||Database Testing Interview Questions|
|CoffeeScript Interview Questions||Automation Testing Interview Questions|
|Software testing Interview Questions||Test Cases Interview Questions|
|Software Development Lifecycle (SDLC) Interview Questions||QUnit Testing Interview Questions|
|Web testing Interview Questions|
Software Qualityassurance An Overview
Software Testing Process
Software Testing Tools An Overview
Source Code Testing Utilities In Unix/linux Environment
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.