Here are some of the topics covered in this book:

• Fundamentals of software testing
• When defects gets introduced in SDLC?
• Why does software have defects?
• What is Verification?
• What is Validation?
• Software Testing Techniques
• Static Testing
• White Box Testing
• Black Box Testing
• Gray Box Testing
• Objectives of Testing
• Software testing Principles
• Reviews
• Types of Reviews
• UI / GUI Testing
• Test Planning
• Test Plan and Test Plan Template
• SRS/FRS template
• Test Scenario
• Example Test Scenarios
• Test Case
• What is a good test case?
• Test case design techniques
• Requirement traceability Matrix (RTM)
• Defect Reporting
• Configuration Management
• Software Configuration Tools

**************************

If you want to stay updated with latest information from software testing industry and more testing free eBooks, please consider signing up for our free newsletter by providing your email address in below sign up form:

Download this eBook:
Just right click on below link and then click on “Save link as” to save this eBook zip file on your computer:

==>> Manual Testing Help eBook Download

If you enjoy this eBook don’t forget to share it with your friends. You can also put all your queries in comments below.

---------------------
I just wanted to thank you for subscribing to SoftwareTestingHelp.com. This blog is a success because of you and your support. Here's to your success!

As always, I appreciate your valuable comments. Visit below link to post your comment:
Manual Testing Help eBook – Free Download Inside!

Thank you so much! ---------------------
Recommended: TestLodge - Online test case management tool - Web based test case management software allowing you to manage your test plans, requirements, test cases and test runs with ease.

1) Performance Testing:

Performance testing is the testing, which is performed, to ascertain how the components of a system are performing, given a particular situation. Resource usage, scalability and reliability of the product are also validated under this testing. This testing is the subset of performance engineering, which is focused on addressing performance issues in the design and architecture of software product.

Performance Testing Goal:

The primary goal of performance testing includes establishing the benchmark behaviour of the system. There are a number of industry-defined benchmarks, which should be met during performance testing.

Performance testing does not aim to find defects in the application, it address a little more critical task of testing the benchmark and standard set for the application. Accuracy and close monitoring of the performance and results of the test is the primary characteristic of performance testing.

Example:

For instance, you can test the application network performance on Connection Speed vs. Latency chart. Latency is the time difference between the data to reach from source to destination. Thus, a 70kb page would take not more than 15 seconds to load for a worst connection of 28.8kbps modem (latency=1000 milliseconds), while the page of same size would appear within 5 seconds, for the average connection of 256kbps DSL (latency=100 milliseconds). 1.5mbps T1 connection (latency=50 milliseconds) would have the performance benchmark set within 1 second to achieve this target.

For example, the time difference between the generation of request and acknowledgement of response should be in the range of x ms (milliseconds) and y ms, where x and y are standard digits. A successful performance testing should project most of the performance issues, which could be related to database, network, software, hardware etc…

2) Load Testing:

Load testing is meant to test the system by constantly and steadily increasing the load on the system till the time it reaches the threshold limit. It is the simplest form of testing which employs the use of automation tools such as LoadRunner or any other good tools, which are available. Load testing is also famous by the names like volume testing and endurance testing.

The sole purpose of load testing is to assign the system the largest job it could possible handle to test the endurance and monitoring the results. An interesting fact is that sometimes the system is fed with empty task to determine the behaviour of system in zero-load situation.

Load Testing Goal:

The goals of load testing are to expose the defects in application related to buffer overflow, memory leaks and mismanagement of memory. Another target of load testing is to determine the upper limit of all the components of application like database, hardware and network etc… so that it could manage the anticipated load in future. The issues that would eventually come out as the result of load testing may include load balancing problems, bandwidth issues, capacity of the existing system etc…

Example:

For example, to check the email functionality of an application, it could be flooded with 1000 users at a time. Now, 1000 users can fire the email transactions (read, send, delete, forward, reply) in many different ways. If we take one transaction per user per hour, then it would be 1000 transactions per hour. By simulating 10 transactions/user, we could load test the email server by occupying it with 10000 transactions/hour.

3) Stress testing

Under stress testing, various activities to overload the existing resources with excess jobs are carried out in an attempt to break the system down. Negative testing, which includes removal of the components from the system is also done as a part of stress testing. Also known as fatigue testing, this testing should capture the stability of the application by testing it beyond its bandwidth capacity.

The purpose behind stress testing is to ascertain the failure of system and to monitor how the system recovers back gracefully. The challenge here is to set up a controlled environment before launching the test so that you could precisely capture the behaviour of system repeatedly, under the most unpredictable scenarios.

Stress Testing Goal:

The goal of the stress testing is to analyse post-crash reports to define the behaviour of application after failure. The biggest issue is to ensure that the system does not compromise with the security of sensitive data after the failure. In a successful stress testing, the system will come back to normality along with all its components, after even the most terrible break down.

Example:

As an example, a word processor like Writer1.1.0 by OpenOffice.org is utilized in development of letters, presentations, spread sheets etc… Purpose of our stress testing is to load it with the excess of characters.

To do this, we will repeatedly paste a line of data, till it reaches its threshold limit of handling large volume of text. As soon as the character size reaches 65,535 characters, it would simply refuse to accept more data. The result of stress testing on Writer 1.1.0 produces the result that, it does not crash under the stress and that it handle the situation gracefully, which make sure that application is working correctly even under rigorous stress conditions.

Further reading – Web Application Load, Stress and Performance Testing Using WAPT.

Have queries on Software Testing? All you need to do is post your questions in the comment section below.

---------------------
I just wanted to thank you for subscribing to SoftwareTestingHelp.com. This blog is a success because of you and your support. Here's to your success!

As always, I appreciate your valuable comments. Visit below link to post your comment:
Difference Between Performance Testing, Load Testing and Stress Testing – With Examples

Thank you so much! ---------------------
Recommended: TestLodge - Online test case management tool - Web based test case management software allowing you to manage your test plans, requirements, test cases and test runs with ease.

Interviews have always been a nerve racking experience. A situation where you are judged on your performance for a job. Everybody gets the jitters when it comes to interviews. Relax! Don’t panic. You need to overcome the nervousness.

Job Interview Tips and advice Applicable for Any Job Seeker Looking for a Dream Job.

No matter which career path you want to choose below are the best tips to help you land your dream job.

1. Always do your homework well before walking into an interview. Make sure you have complete knowledge about the company and the role.

2. Know yourself. Remember first impression is the last impression. Demonstrate your capabilities and qualities and how well you can serve them. Don’t be overconfident and aggressive.

3. You should know your competency and transferable skills. Competency skills are the skills matching your job profile and transferable skills which you acquired through other jobs, personal activities.

4. Social networking sites like Facebook, Orkut, Linkedin can be used for work opportunities and conversing with other people improving your interpersonal skills.

5. Be clear about what you want to achieve in life and about your career objective. It will keep you focused. You don’t have to do anything for the heck of it.

6. Your CV is vital for a successful interview. Never bluff, include all your skills and experience to give you a competitive edge.

7. Prepare well for an interview. You can make notes of interview questions which are most likely to be asked. Practice your answers. This will boost your confidence.

8. Work on your communication skills. Remember having a good technical knowledge without effective interpersonal skills will not take you anywhere. Be expressive and a good conversationalist. Dazzle the interviewers with eloquent speech.

9. Make sure you can support your strengths by giving examples. You can prepare before but don’t falter while talking. It will not create a good impression.

10. When asked about your weaknesses acknowledge them. If you are not able to describe, it signifies that you lack self awareness. You can’t be perfect in everything.

11. Always be presentable while dressing for the interview. Your attire should be according to the role, culture and yourself. Please no tacky and brash clothing and accessories. You don’t need to be glammed up.

12. Spend time on personal grooming. This will keep you calm. You don’t have to present yourself as a person full of nervous energy and fidgets.

13. On the D day, relax. Be comfortable and wear a smile. And Voila! You will definitely crack the interview.

14. Your body language is very important. Your facial expressions, hand movements, posture, voice and pace should send the same message.

15. Don’t forget to make an eye contact. Your voice should be enthusiastic and do not stammer. Lack of enthusiasm will put off the interviewers.

16. Keep all your documents well organized in a folder. Also be on time, preferably 15 minutes before so you get time to settle down and calm your nerves.

17. Interview manners are very important. Bad manners will definitely be a turn off. Don’t bang the door, shake handily firmly, ask if you can take a seat, sit up straight and do not slouch.

18. When asked about remuneration. You don’t have to be blunt. Instead you can say that you expect a fair raise in terms of qualifications and experience proportionate with peers.
Now that you have some good interview tips. Be confident, gear up and don’t let yourself down. Remember this is not the end of life if you don’t get through to the process. It’s just an interview. Good Luck!

---------------------
I just wanted to thank you for subscribing to SoftwareTestingHelp.com. This blog is a success because of you and your support. Here's to your success!

As always, I appreciate your valuable comments. Visit below link to post your comment:
18 Tips to Handle Any Job Interview Successfully

Thank you so much! ---------------------
Recommended: TestLodge - Online test case management tool - Web based test case management software allowing you to manage your test plans, requirements, test cases and test runs with ease.

As Software testers, we keep performing testing activities in various phases of a project. When it comes to testing our own skills, we may not end up choosing an appropriate approach. I am talking about how the interview rounds go and how to face them. The whole article is a very general discussion about the challenges that a tester has to face in an interview.

Let’s start with preparing a CV for software testing job profile.

How to prepare a good CV?
By the term ‘Good’ I mean a CV that describes best about your skills, your expertise, your strengths etc. It’s better not to use a same CV for different types of job profiles. Making slight changes will help to get a call. For e.g. you can highlight the skill set that you posses for the required job like any automation tool or experience in other related automation tools. You can also add about the basic knowledge of any technologies that you posses. This may be an added advantage.

Preparation before the job interview:

Before attending the interview, check the job profile in detail. Understand if the requirement is purely in manual testing, Automation testing or on both. Check if your job profile experience match with what is expected.
The interviewer will mostly stick to questions around the given job profile and what you have mentioned in your CV.  Make sure you can answer questions confidently which are based on your CV. It depends on how the discussion goes between the candidate and the interviewer, which leads to discussion in other areas.

Appear confidently at the time of interview:

In most cases, the interview starts with a brief up about the candidate. One can answer to this question by following a sequence like starting with your Name, what qualifications do you posses, how you started your career as a software tester etc. Some interviewers do not like to hear about personal details like family. So do not proceed with these details unless the interviewer asks for it.

While answering any question tell what you know. Do not try to explain about ideal cases. Interviewers are interested in practical approach, rather than ideal cases. Tell the interviewer how you will go about solving the problems or about your way of tackling things. Do not talk anything negative about any person especially about developers/programmers. If you do so, then it shows that you are not mature enough. Now a days in most of the interviews, scenarios are cited rather than direct question and answer. If the scenario is new to you, take few seconds to think on it and then answer. Do not hurry up things.

The way you present in interviews is very important. Right attitude is very important too. Many managers can judge it easily, if you have really worked on projects or it’s just a fake experience. The confidence level with which you answer makes a strong impression. For any question if you are not sure about the correct answer, just make an attempt. Do not just give up. You can also talk about things that you explored in free time or with your interest. This shows that you take initiative and are a continuous learner as well.

As many of us must have experienced that the interviewers keep asking about the processes that you have followed or are familiar with. One does not need to worry if they have never followed any processes. Following the processes is up to the company and a tester cannot do much regarding that. But of course one can follow some processes for his/her own task (I mean the modules that you own or are in charge of etc). This will not only help to manage things but also inspires other to follow some processes. Any process, which has proven some good results, can be followed. So, instead of blaming others for not following any processes, one can take an initiative to do it. Do not forget that Initiative is one of the qualities that a tester should possess.

One more important point: It’s not necessary that the person who is taking your interview is a person from QA background. A person from developing background can also take software testing job interviews. What I mean to say is the person need not have actually worked on the QA processes. In such case it becomes very important to answer the questions very carefully. It may sound illogical when a person from non-QA background interviews a tester but remember it will be a very good experience as you will get to know how testing is perceived by others.

Over to You:
What’s your experience about software testing interviews? If you want to share some do’s and don’ts please make comments below so that other testers can get benefit from your experience. And finally ‘all the best’ for your testing career!

---------------------
I just wanted to thank you for subscribing to SoftwareTestingHelp.com. This blog is a success because of you and your support. Here's to your success!

As always, I appreciate your valuable comments. Visit below link to post your comment:
Preparing For Software Testing Interview – Simple Tips To Follow Prior And at The Time of Interview

Thank you so much! ---------------------
Recommended: TestLodge - Online test case management tool - Web based test case management software allowing you to manage your test plans, requirements, test cases and test runs with ease.

This is a guest article by “N. Sandhya Rani”.

ISTQB ‘Foundation level’ sample questions with answers and detailed evaluation of each option:

1. Methodologies adopted while performing Maintenance Testing:-
a) Breadth Test and Depth Test
b) Retesting
c) Confirmation Testing
d) Sanity Testing

Evaluating the options:
a) Option a: Breadth testing is a test suite that exercises the full functionality of a product but does not test features in detail. Depth testing is a test that exercises a feature of a product in full detail.
b) Option b: Retesting is part of regression
c) Option c: Confirmation testing is a synonym for retesting
d) Option d: Sanity testing does not include full functionality
Maintenance testing includes testing some features in detail (for e.g. environment) and for some features detail testing is not required. It’s a mix of both breadth and depth testing.

So, the answer is ‘A’

2. Which of the following is true about Formal Review or Inspection:-
i. Led by Trained Moderator (not the author).
ii. No Pre Meeting Preparations
iii. Formal Follow up process.
iv. Main Objective is to find defects

a) ii is true and i,iii,iv are false
b) i,iii,iv are true and ii is false
c) i,iii,iv are false and ii is true
d) iii is true and i,ii,iv are false

Evaluating the options:
Consider the first point (i). This is true, Inspection is led by trained moderator. Hence we can eliminate options (a) and (d). Now consider second point. In Inspection pre-meeting preparation is required. So this point is false. Look for option where (i) is true and (ii) is false.

The answer is ‘B’

3. The Phases of formal review process is mentioned below arrange them in the correct order.

i. Planning
ii. Review Meeting
iii. Rework
iv. Individual Preparations
v. Kick Off
vi. Follow Up

a) i,ii,iii,iv,v,vi
b) vi,i,ii,iii,iv,v
c) i,v,iv,ii,iii,vi
d) i,ii,iii,v,iv,vi

Evaluating the options:
Formal review process is ’Inspection’. Planning is foremost step. Hence we can eliminate option ’b’. Now we need to kickoff the process, so the second step will be Kick off. That’s it we found the answer. Its ’C’

The answer is ’C’

4. Consider the following state transition diagram of a two-speed hair dryer, which is operated by pressing its one button. The first press of the button turns it on to Speed 1, second press to Speed 2 and the third press turns it off.

Which of the following series of state transitions below will provide 0-switch coverage?
a. A,C,B
b. B,C,A
c. A,B,C
d. C,B,A

Evaluating the options:
In State transition testing a test is defined for each state transition. The coverage that is achieved by this testing is called 0-switch or branch coverage. 0-switch coverage is to execute each loop once (No repetition. We should start with initial state and go till end state. It does not test ‘sequence of two state transitions’). In this case the start state is ‘OFF’, and then press of the button turns it on to Speed 1 (i.e. A). Second press turns it on to Speed 2 (i.e. B) and the third press turns it off (i.e. C). Here we do not test the combinations like what if the start state is ‘Speed 1’ or ‘Speed 2’ etc.

An alternate way of solving this is check for the options where it starts with ‘OFF’ state. So we have options ‘a’ and ‘c’ to select from. As per the state diagram from ‘OFF’ state the dryer goes to ‘Speed 1’ and then to ‘Speed 2’. So our answer should start with ‘A’ and end with ‘C’.

The answer is ’C’

5. White Box Techniques are also called as :-
a) Structural Testing
b) Design Based Testing
c) Error Guessing Technique
d) Experience Based Technique

Evaluating the options:
I guess no evaluation is required here. It’s a straight answer. White box techniques are also called as Structural testing. (as it is done using code)

The answer is ‘A’

6. What is an equivalence partition (also known as an equivalence class)?
a) A set of test cases for testing classes of objects
b) An input or output range of values such that only one value in the range becomes a test case
c) An input or output range of values such that each value in the range becomes a test case
d) An input or output range of values such that every tenth value in the range becomes a test case.

Evaluating the options:
Let’s recall the definition of equivalence partition. It is grouping inputs into valid and invalid classes. Hence any one value from one particular class forms an input. For e.g. input a valid class contains values from 3-5, then any value between 3-5 is considered as an input. All values are supposed to yield same output. Hence one value in this range becomes a test case.

The answer is ‘B’

7. The Test Cases Derived from use cases
a) Are most useful in uncovering defects in the process flows during real world use of the system
b) Are most useful in uncovering defects in the process flows during the testing use of the system
c) Are most useful in covering the defects in the process flows during real world use of the system
d) Are most useful in covering the defects at the Integration Level

Evaluating the options:
Please refer to Use case related topic in the foundation level guide “Use cases describe the “process flows” through a system based on its actual likely use” (actual likely use is nothing but the real world use of the system). Use cases are useful for uncovering defects. Hence we can eliminate options (c ) and (d). Use case uncovers defects in process flow during real world use of the system.

The answer is ‘A’

8. Exhaustive Testing is
a) Is impractical but possible
b) Is practically possible
c) Is impractical and impossible
d) Is always possible

Evaluating the options:
From the definition given in the syllabus, Exhaustive testing is impossible. But it is possible in trivial cases. Exhaustive testing is not always possible. So eliminate option ‘d’. It is not impossible also. So eliminate option ‘c’. But implementing is impractical. Hence we can conclude that exhaustive testing is impractical but possible

The answer is ‘A’

9. Which of the following is not a part of the Test Implementation and Execution Phase
a) Creating test suites from the test cases
b) Executing test cases either manually or by using test execution tools
c) Comparing actual results
d) Designing the Tests

Evaluating the options:
Please take care of the word ‘not’ in the question. Test implementation does include Creating test suites, executing and comparing results. Hence eliminate options a, b and c. The only option left is ‘D’. Designing activities come before implementation.

The answer is ‘D’

10. Which of the following techniques is NOT a White box technique?
a) Statement Testing and coverage
b) Decision Testing and coverage
c) Condition Coverage
d) Boundary value analysis

Evaluating the options:
Please take care of the word ‘not’ in the question. We have to choose the one which is not a part of white box technique. Statement, decision, condition are the terms used in white box. So eliminate options a, b and c. Boundary value is part of black box.

The answer is ‘D’

11. A Project risk includes which of the following
a) Organizational Factors
b) Poor Software characteristics
c) Error Prone software delivered.
d) Software that does not perform its intended functions

Evaluating the options:
a) Option a: Organizational factors can be part of project risk.
b) Option b: Poor software characteristics are part of software. Its not a risk
c) Option c: Error prone software delivered. Again it’s a part of software.
d) Option d: Software that does not perform its intended functions. Again it’s a part of software.

The answer is ‘A’

12. In a risk-based approach the risks identified may be used to :
i. Determine the test technique to be employed
ii. Determine the extent of testing to be carried out
iii. Prioritize testing in an attempt to find critical defects as early as possible.
iv. Determine the cost of the project

a) ii is True; i, iii, iv & v are False
b) i,ii,iii are true and iv is false
c) ii & iii are True; i, iv are False
d) ii, iii & iv are True; i is false

Evaluating the options:
a) Option a: Risks identified can be used to determine the test technique.
b) Option b: Risks can be used to determine the extent of testing required. For e.g. if there are P1 bugs in a software, then it is a risk to release it. Hence we can increase the testing cycle to reduce the risk
c) Option c: If risk areas are identified before hand, then we can prioritize testing to find defects asap.
d) Option d: Risk does not determine the cost of the project. It determines the impact on the project as a whole.
Check for the option where first 3 points are true. Its ‘B’

The answer is ‘B’

13. Which of the following is the task of a Tester?
i. Interaction with the Test Tool Vendor to identify best ways to leverage test tool on the project.
ii. Prepare and acquire Test Data
iii. Implement Tests on all test levels, execute and log the tests.
iv. Create the Test Specifications

a) i, ii, iii is true and iv is false
b) ii,iii,iv is true and i is false
c) i is true and ii,iii,iv are false
d) iii and iv is correct and i and ii are incorrect

Evaluating the options:
Not much explanation is needed in this case. As a tester, we do all the activities mentioned in options (ii), (iii) and (iv).

The answer is ‘B’

14. The Planning phase of a formal review includes the following :-
a) Explaining the objectives
b) Selecting the personnel, allocating roles.
c) Follow up
d) Individual Meeting preparations

Evaluating the options:
In this case, elimination will work best. Follow-up is not a planning activity. It’s a post task. Hence eliminate option ‘b’. Individual meeting preparation is an activity for individual. It’s not a planning activity. Hence eliminate option ‘d’. Now we are left with 2 options ‘a’ and ‘b’, read those 2-3 times. We can identify that option ‘b’ is most appropriate. Planning phase of formal review does include selecting personnel and allocation of roles. Explaining the objectives is not part of review process. (this is also written in the FL syllabus)

The answer is ‘B’

15. A Person who documents all the issues, problems and open points that were identified during a formal review.
a) Moderator.
b) Scribe
c) Author
d) Manager

Evaluating the options:
I hope there is not confusion here. The answer is scribe.

The answer is ‘B’

16. Who are the persons involved in a Formal Review :-
i. Manager
ii. Moderator
iii. Scribe / Recorder
iv. Assistant Manager

a) i,ii,iii,iv are true
b) i,ii,iii are true and iv is false.
c) ii,iii,iv are true and i is false.
d) i,iv are true and ii, iii are false.

Evaluating the options:
The question is regarding formal review, means Inspection. First we will try to identify the persons that we are familiar w.r.t Inspection. Manager, Moderator and Scribe are involved in Inspection. So now we have only first 2 options to select from. (other 2 options are eliminated). There is no assistant manager in Inspection.

The answer is ‘B’

17. Which of the following is a Key Characteristics of Walk Through
a) Scenario , Dry Run , Peer Group
b) Pre Meeting Preparations
c) Formal Follow Up Process
d) Includes Metrics

Evaluating the options:
Pre meeting preparation is part of Inspection. Also Walk through is not a formal process. Metrics are part of Inspection. Hence eliminating ‘b’, ‘c’ and ‘d’.

The answer is ‘A’

18. What can static analysis NOT find?
a) the use of a variable before it has been defined
b) unreachable (“dead”) code
c) memory leaks
d) array bound violations

Evaluating the options:
Static analysis cover all the above options except ‘Memory leaks’. (Please refer to the FL syllabus. Its written clearly over there)

The answer is ‘C’

19. Incidents would not be raised against:
a) requirements
b) documentation
c) test cases
d) improvements suggested by users

Evaluating the options:
The first three options are obvious options for which incidents are raised. The last option can be thought as an enhancement. It is a suggestion from the users and not an incident.

The answer is ‘D’

20. A Type of functional Testing, which investigates the functions relating to detection of threats, such as virus from malicious outsiders.
a) Security Testing
b) Recovery Testing
c) Performance Testing
d) Functionality Testing

Evaluating the options:
The terms used in the question like detection of threats, virus etc point towards the security issues. Also security testing is a part of Functional testing. In security testing we investigate the threats from malicious outsiders etc.

The answer is ‘A’

21. Which of the following is not a major task of Exit criteria?
a) Checking test logs against the exit criteria specified in test planning.
b) Logging the outcome of test execution.
c) Assessing if more tests are needed.
d) Writing a test summary report for stakeholders.

Evaluating the options:
The question is about ‘not’ a major task. Option ‘a’ is a major task. So eliminate this. Option ‘b’ is not a major task. (But yes, logging of outcome is important). Option ‘c’ and ‘d’ both are major tasks of Exit criteria. So eliminate these two.

The answer is ‘B’

22. Testing where in we subject the target of the test , to varying workloads to measure and evaluate the performance behaviors and ability of the target and of the test to continue to function properly under these different workloads.
a) Load Testing
b) Integration Testing
c) System Testing
d) Usability Testing

Evaluating the options:
Workloads, performance are terms that come under Load testing. Also as can be seen from the other options, they are not related to load testing. So we can eliminate them.

The answer is ‘A’

23. Testing activity which is performed to expose defects in the interfaces and in the interaction between integrated components is :-
a) System Level Testing
b) Integration Level Testing
c) Unit Level Testing
d) Component Testing

Evaluating the options:
We have to identify the testing activity which finds defects which occur due to interaction or integration. Option ‘a’ is not related to integration. Option ‘c’ is unit testing. Option ‘d’ component is again a synonym for unit testing. Hence eliminating these three options.

The answer is ‘B’

24. Static analysis is best described as:
a) The analysis of batch programs.
b) The reviewing of test plans.
c) The analysis of program code.
d) The use of black box testing.

Evaluating the options:
In this case we have to choose an option, which ‘best’ describes static analysis. Most of the options given here are very close to each other. We have to carefully read them.
a) Option a: Analysis is part of static analysis. But is not the best option which describes static analysis.
b) Option b: Reviews are part of static analysis. But is not the best option which describes static analysis.
c) Option c: Static analysis does analyze program code.
d) Option d: This option ca be ruled out, as black box is a dynamic testing.

The answer is ‘C’

25. One of the fields on a form contains a text box which accepts alpha numeric values. Identify the Valid Equivalence class
a) BOOK
b) Book
c) Boo01k
d) book

Evaluating the options:
As we know, alpha numeric is combination of alphabets and numbers. Hence we have to choose an option which has both of these.
a. Option a: contains only alphabets. (to create confusion they are given in capitals)
b. Option b: contains only alphabets. (the only difference from above option is that all letters are not in capitals)
c. Option c: contains both alphabets and numbers
d. Option d: contains only alphabets but in lower case

The answer is ‘C’

26. Reviewing the test Basis is a part of which phase
a) Test Analysis and Design
b) Test Implementation and execution
c) Test Closure Activities
d) Evaluating exit criteria and reporting

Evaluating the options:
Test basis comprise of requirements, architecture, design, interfaces. By looking at these words, we can straight away eliminate last two options. Now option ‘a’ is about test analysis and design. This comes under test basis. Option ‘b’ is about implementation and execution which come after the design process. So the best option is ‘a’.

The answer is ‘A’

27. Reporting Discrepancies as incidents is a part of which phase :-
a) Test Analysis and Design
b) Test Implementation and execution
c) Test Closure Activities
d) Evaluating exit criteria and reporting

Evaluating the options:
Incident is reporting discrepancies, in other terms its defect/bug. We find defects while execution cycle where we execute the test cases.

The answer is ‘B’

28. Which of the following items would not come under Configuration Management?
a) operating systems
b) test documentation
c) live data
d) user requirement document

Evaluating the options:
We have to choose an option which does ‘not’ come under Configuration Management (CM). CM is about maintaining the integrity of the products like components, data and documentation.
a) Option a: maintaining the Operating system configuration that has been used in the test cycle is part of CM.
b) Option b: Test documentation is part of CM
c) Option c: Data is part of CM. but here the option is ‘live data’ which is not part of CM. The live data keeps on changing (in real scenario).
d) Option d: Requirements and documents are again part of CM
The only option that does not fall under CM is ‘c’

The answer is ‘C’

29. Handover of Test-ware is a part of which Phase
a) Test Analysis and Design
b) Test Planning and control
c) Test Closure Activities
d) Evaluating exit criteria and reporting

Evaluating the options:
Hand over is typically a process which is part of closure activities. It is not part of analysis, design or planning activity. Also it is not part of evaluating exit criteria. After closure of test cycle test-ware is handover to the maintenance organization.

The answer is ‘C’

30. The Switch is switched off once the temperature falls below 18 and then it is turned on when the temperature is more than 21. Identify the Equivalence values which belong to the same class.
a) 12,16,22
b) 24,27,17
c) 22,23,24
d) 14,15,19

Evaluating the options:
Read the question carefully. We have to choose values from same class. So first divide the classes. When temperature falls below 18 switch is turned off. This forms a class (as shown below). When the temperature is more than 21, the switch is turned on. For values between 18 to 21, no action is taken. This also forms a class as shown below.

Class I: less than 18 (switch turned off)
Class II: 18 to 21
Class III: above 21 (switch turned on)

From the given options select the option which has values from only one particular class. Option ‘a’ values are not in one class, so eliminate. Option ‘b’ values are not in one class, so eliminate. Option ‘c’ values are in one class. Option ‘d’ values are not in one class, so eliminate. (please note that the question does not talk about valid or invalid classes. It is only about values in same class)

The answer is ‘C’

About the Author:
“N. Sandhya Rani” is having around 4 years of experience in software testing mostly in manual testing. She is helping many aspirant software testers to clear the ISTQB testing certification exam by giving tips on how to solve the multiple choice questions correctly with evaluating each option quickly.

If you have any query on ISTQB testing certification exam, please post it in comment section below.

---------------------
I just wanted to thank you for subscribing to SoftwareTestingHelp.com. This blog is a success because of you and your support. Here's to your success!

As always, I appreciate your valuable comments. Visit below link to post your comment:
ISTQB software testing certification sample question paper with answers – Part II

Thank you so much! ---------------------
Recommended: TestLodge - Online test case management tool - Web based test case management software allowing you to manage your test plans, requirements, test cases and test runs with ease.

Sandhya will be giving you ISTQB paper pattern and tips on how to solve the questions quickly. To start with, here are 10 sample ISTQB ‘Foundation level’ questions with detailed explanation for answers.

ISTQB question pattern and tips to solve:
ISTQB questions are formatted in such a way that the answers look very much similar. People often choose the one, which they are more familiar with. We should carefully read the question twice or thrice or may be more than that, till we are clear about what is being asked in the question.

Now look at the options carefully. The options are chosen to confuse the candidates. To choose the correct answer, we should start eliminating one by one. Go through each option and check whether it is appropriate or not. If you end up selecting more than one option, repeat the above logic for the answers that you selected. This will definitely work.

Before you start with the question papers, please read the material thoroughly. Practice as many papers as possible. This will help a lot because, when we actually solve the papers, we apply the logic that we know.

ISTQB ‘Foundation level’ sample questions with answers:

1. Designing the test environment set-up and identifying any required infrastructure and tools are a part of which phase

a) Test Implementation and execution
b) Test Analysis and Design
c) Evaluating the Exit Criteria and reporting
d) Test Closure Activities

Evaluating the options:
a) Option a: as the name suggests these activities are part of the actual implementation cycle. So do not fall under set-up
b) Option b: Analysis and design activities come before implementation. The test environment set-up, identifying any required infrastructure and tools are part of this activity.
c) Option c: These are post implementation activities
d) Option d: These are related to closing activities. This is the last activity.

So, the answer is ‘B’

2. Test Implementation and execution has which of the following major tasks?

i. Developing and prioritizing test cases, creating test data, writing test procedures and optionally preparing the test harnesses and writing automated test scripts.
ii. Creating the test suite from the test cases for efficient test execution.
iii. Verifying that the test environment has been set up correctly.
iv. Determining the exit criteria.

a) i,ii,iii are true and iv is false
b) i,,iv are true and ii is false
c) i,ii are true and iii,iv are false
d) ii,iii,iv are true and i is false

Evaluating the options:
Let’s follow a different approach in this case. As can be seen from the above options, determining the exit criteria is definitely not a part of test implementation and execution. So choose the options where (iv) is false. This filters out ‘b’ and ‘d’.

We need to select only from ‘a’ and ‘c’. We only need to analyze option (iii) as (i) and (ii) are marked as true in both the cases. Verification of the test environment is part of the implementation activity. Hence option (iii) is true. This leaves the only option as ‘a’.

So, the answer is ‘A’

3. A Test Plan Outline contains which of the following:-

i. Test Items
ii. Test Scripts
iii. Test Deliverables
iv. Responsibilities

a) I,ii,iii are true and iv is false
b) i,iii,iv are true and ii is false
c) ii,iii are true and i and iv are false
d) i,ii are false and iii , iv are true

Evaluating the options:
Let’s use the approach given in question no. 2. Test scripts are not part of the test plan (this must be clear). So choose the options where (ii) is false. So we end up selecting ‘b’ and ‘d’. Now evaluate the option (i), as option (iii) and (iv) are already given as true in both the cases. Test items are part of the test plan. Test items are the modules or features which will be tested and these will be part of the test plan.

So, the answer is ‘B’

4. One of the fields on a form contains a text box which accepts numeric values in the range of 18 to 25. Identify the invalid Equivalence class
a) 17
b) 19
c) 24
d) 21

Evaluating the options:
In this case, first we should identify valid and invalid equivalence classes.

Invalid Class | Valid Class | Invalid Class
Below 18 | 18 to 25 | 26 and above

Option ‘a’ falls under invalid class. Options ‘b’, ‘c’ and ‘d’ fall under valid class.

So, the answer is ‘A’

5. In an Examination a candidate has to score minimum of 24 marks in order to clear the exam. The maximum that he can score is 40 marks. Identify the Valid Equivalence values if the student clears the exam.

a) 22,23,26
b) 21,39,40
c) 29,30,31
d) 0,15,22

Evaluating the options:
Let’s use the approach given in question 4. Identify valid and invalid equivalence classes.

Invalid Class | Valid Class | Invalid Class
Below 24 | 24 to 40 | 41 and above

The question is to identify valid equivalence values. So all the values must be from ‘Valid class’ only.

a) Option a: all the values are not from valid class
b) Option b: all the values are not from valid class
c) Option c: all the values are from valid class
d) Option d: all the values are not from valid class

So, the answer is ‘C’

6. Which of the following statements regarding static testing is false:

a) static testing requires the running of tests through the code
b) static testing includes desk checking
c) static testing includes techniques such as reviews and inspections
d) static testing can give measurements such as cyclomatic complexity

Evaluating the options:
a) Option a: is wrong. Static testing has nothing to do with code
b) Option b: correct, static testing does include desk checking
c) Option c: correct, it includes reviews and inspections
d) Option d: correct, it can give measurements such as cyclomatic complexity

So, the answer is ‘A’

7. Verification involves which of the following:-
i. Helps to check the Quality of the built product
ii. Helps to check that we have built the right product.
iii. Helps in developing the product
iv. Monitoring tool wastage and obsoleteness.

a) Options i,ii,iii,iv are true.
b) i is true and ii,iii,iv are false
c) i,ii,iii are true and iv is false
d) ii is true and i,iii,iv are false.

Evaluating the options:
a) Option a: The quality of the product can be checked only after building it.
Verification is a cycle before completing the product.
b) Option b: Verification checks that we have built the right product.
c) Option c: it does not help in developing the product
d) Option d: it does not involve monitory activities.

So, the answer is ‘B’

8. Component Testing is also called as :-
i. Unit Testing
ii. Program Testing
iii. Module Testing
iv. System Component Testing .

a) i,ii,iii are true and iv is false
b) i,ii,iii,iv are false
c) i,ii,iv are true and iii is false
d) all of above is true

Evaluating the options:
a) Option a: correct, component testing is also called as unit testing
b) Option b: not sure (but as all the options indicate this as true, we can conclude that Program testing is also called as unit testing)
c) Option c: correct, component testing is also called as module testing
d) Option d: wrong. System component testing comes under system testing.

So, the answer is ‘A’

9. Link Testing is also called as :
a) Component Integration testing
b) Component System Testing
c) Component Sub System Testing
d) Maintenance testing

Evaluating the options:
As the name suggests, this testing is performed by linking (say modules). Now if
we look at the options, only option ‘a’ is performed by linking or integrating
modules/components.

So, the answer is ‘A’

10.

What is the expected result for each of the following test cases?
A.TC1: Anand is a 32 year old married, residing in Kolkatta.
B.TC3: Attapattu is a 65 year old married person, residing in Colombo.
a) A – Issue membership, 10% discount, B–Issue membership, offer no discount. B
b) A – Don’t Issue membership, B – Don’t offer discount. C
c) A – Issue membership, no discount, B – Don’t Issue membership.
d) A – Issue membership, no discount, B- Issue membership with 10% discount.

Evaluating the options:

Explanation:
For TC1: follow the path in green color
(The person is Indian resident, so select only ‘True’ options.
The person is aged between 18-55, so select only ‘True’
The person is a married, so again select only ‘True’
For this person, the actions under ‘Rule 4′ will be applied. That is, issue membership and no discount)

For TC3: follow the path in blue color
(The person is not Indian resident, so select only ‘False’ (under Rule 1)
The person is not aged between 18-55. No need to select any path, as it is written “Don’t care”.
The person is married. No need to select any path, as it is written “Don’t care”.
For this person, the actions under ‘Rule1′ will be applied, That is, Don’t issue membership and no discount.)

So, the answer is ‘C’

Note: The answers are based on writers own experience and judgment and may not be 100% correct. If you feel any correction is required please discuss in comments below.

Please feel free to ask any question related to ISTQB exam and testing certifications in comment section below.

---------------------
I just wanted to thank you for subscribing to SoftwareTestingHelp.com. This blog is a success because of you and your support. Here's to your success!

As always, I appreciate your valuable comments. Visit below link to post your comment:
ISTQB question pattern and tips to solve

Thank you so much! ---------------------
Recommended: TestLodge - Online test case management tool - Web based test case management software allowing you to manage your test plans, requirements, test cases and test runs with ease.

Boundary value analysis and equivalence partitioning both are test case design strategies in black box testing.

Equivalence Partitioning:

In this method the input domain data is divided into different equivalence data classes. This method is typically used to reduce the total number of test cases to a finite set of testable test cases, still covering maximum requirements.

In short it is the process of taking all possible test cases and placing them into classes. One test value is picked from each class while testing.

E.g.: If you are testing for an input box accepting numbers from 1 to 1000 then there is no use in writing thousand test cases for all 1000 valid input numbers plus other test cases for invalid data.

Using equivalence partitioning method above test cases can be divided into three sets of input data called as classes. Each test case is a representative of respective class.

So in above example we can divide our test cases into three equivalence classes of some valid and invalid inputs.

Test cases for input box accepting numbers between 1 and 1000 using Equivalence Partitioning:
1) One input data class with all valid inputs. Pick a single value from range 1 to 1000 as a valid test case. If you select other values between 1 and 1000 then result is going to be same. So one test case for valid input data should be sufficient.

2) Input data class with all values below lower limit. I.e. any value below 1, as a invalid input data test case.

3) Input data with any value greater than 1000 to represent third invalid input class.

So using equivalence partitioning you have categorized all possible test cases into three classes. Test cases with other values from any class should give you the same result.

We have selected one representative from every input class to design our test cases. Test case values are selected in such a way that largest number of attributes of equivalence class can be exercised.

Equivalence partitioning uses fewest test cases to cover maximum requirements.

Boundary value analysis:

It’s widely recognized that input values at the extreme ends of input domain cause more errors in system. More application errors occur at the boundaries of input domain. ‘Boundary value analysis’ testing technique is used to identify errors at boundaries rather than finding those exist in center of input domain.

Boundary value analysis is a next part of Equivalence partitioning for designing test cases where test cases are selected at the edges of the equivalence classes.

Test cases for input box accepting numbers between 1 and 1000 using Boundary value analysis:
1) Test cases with test data exactly as the input boundaries of input domain i.e. values 1 and 1000 in our case.

2) Test data with values just below the extreme edges of input domains i.e. values 0 and 999.

3) Test data with values just above the extreme edges of input domain i.e. values 2 and 1001.

Boundary value analysis is often called as a part of stress and negative testing.

Note: There is no hard-and-fast rule to test only one value from each equivalence class you created for input domains. You can select multiple valid and invalid values from each equivalence class according to your needs and previous judgments.

E.g. if you divided 1 to 1000 input values in valid data equivalence class, then you can select test case values like: 1, 11, 100, 950 etc. Same case for other test cases having invalid data classes.

This should be a very basic and simple example to understand the Boundary value analysis and Equivalence partitioning concept.

Share your examples below.

---------------------
I just wanted to thank you for subscribing to SoftwareTestingHelp.com. This blog is a success because of you and your support. Here's to your success!

As always, I appreciate your valuable comments. Visit below link to post your comment:
What is Boundary value analysis and Equivalence partitioning?

Thank you so much! ---------------------
Recommended: TestLodge - Online test case management tool - Web based test case management software allowing you to manage your test plans, requirements, test cases and test runs with ease.

Ok, I am asking to many questions without giving answer to any of it. Well, each question mentioned above will require a separate post to address the problem fairly. Here we will address in short about – How to hire the right candidates for software testing positions?

Companies or interviewers, who are not serious about hiring right candidates, often end with hiring poor performers.

What I mean by “Not serious” here?
- They don’t know why and for what post they are hiring a candidate.
- They either fake or fail to post the exact job opening details.
- Or they don’t want to hire skilled performers at all. Hmm, jealousy might be the key here!

Whichever is the reason, there is definitely loss of organization. Loss in terms of both revenue and growth.

If you need answer to these questions, here is an informative video from Pradeep Soundararajan – Consulting tester of Satisfice Inc in India. He explained what is the current situation of software testing interview process in India and how interviewers are wrong in selecting questions to be asked to candidates. A nice start to spread the awareness and importance of software testing interviews.

Current Software Testing Interview situation:

Click on the bottom right button to see the video in full screen.

You can watch his more video’s on software testing here.

Do not forget to comment your experience on software testing interviews, either as an interviewer or as a candidate.

Related article: Choosing software testing as your career.

---------------------
I just wanted to thank you for subscribing to SoftwareTestingHelp.com. This blog is a success because of you and your support. Here's to your success!

As always, I appreciate your valuable comments. Visit below link to post your comment:
How to hire the right candidates for software testing positions?

Thank you so much! ---------------------
Recommended: TestLodge - Online test case management tool - Web based test case management software allowing you to manage your test plans, requirements, test cases and test runs with ease.

Here are the differences you can see:

SMOKE TESTING:

• Smoke testing originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch fire and smoke. In software industry, smoke testing is a shallow and wide approach whereby all areas of the application without getting into too deep, is tested.
• A smoke test is scripted, either using a written set of tests or an automated test
• A Smoke test is designed to touch every part of the application in a cursory way. It’s shallow and wide.
• Smoke testing is conducted to ensure whether the most crucial functions of a program are working, but not bothering with finer details. (Such as build verification).
• Smoke testing is normal health check up to a build of an application before taking it to testing in depth.

SANITY TESTING:

• A sanity test is a narrow regression test that focuses on one or a few areas of functionality. Sanity testing is usually narrow and deep.
• A sanity test is usually unscripted.
• A Sanity test is used to determine a small section of the application is still working after a minor change.
• Sanity testing is a cursory testing, it is performed whenever a cursory testing is sufficient to prove the application is functioning according to specifications. This level of testing is a subset of regression testing.
• Sanity testing is to verify whether requirements are met or not, checking all features breadth-first.

Hope these points will help you to clearly understand the Smoke and sanity tests and will help to remove any confusion.

Thanks to VijayD for answering this question in simple way for our readers.

If you have more points on smoke and sanity testing to elaborate on, please comment below.

---------------------
I just wanted to thank you for subscribing to SoftwareTestingHelp.com. This blog is a success because of you and your support. Here's to your success!

As always, I appreciate your valuable comments. Visit below link to post your comment:
Smoke testing and sanity testing – Quick and simple differences

Thank you so much! ---------------------
Recommended: TestLodge - Online test case management tool - Web based test case management software allowing you to manage your test plans, requirements, test cases and test runs with ease.

Question:

What is the difference between client-server testing and web based testing and what are things that we need to test in such applications?

Ans:
Projects are broadly divided into two types of:

• 2 tier applications
• 3 tier applications

CLIENT / SERVER TESTING
This type of testing usually done for 2 tier applications (usually developed for LAN)
Here we will be having front-end and backend.

The application launched on front-end will be having forms and reports which will be monitoring and manipulating data

E.g: applications developed in VB, VC++, Core Java, C, C++, D2K, PowerBuilder etc.,
The backend for these applications would be MS Access, SQL Server, Oracle, Sybase, Mysql, Quadbase

The tests performed on these types of applications would be
- User interface testing
- Manual support testing
- Functionality testing
- Compatibility testing & configuration testing
- Intersystem testing

WEB TESTING
This is done for 3 tier applications (developed for Internet / intranet / xtranet)
Here we will be having Browser, web server and DB server.

The applications accessible in browser would be developed in HTML, DHTML, XML, JavaScript etc. (We can monitor through these applications)

Applications for the web server would be developed in Java, ASP, JSP, VBScript, JavaScript, Perl, Cold Fusion, PHP etc. (All the manipulations are done on the web server with the help of these programs developed)

The DBserver would be having oracle, sql server, sybase, mysql etc. (All data is stored in the database available on the DB server)

The tests performed on these types of applications would be
- User interface testing
- Functionality testing
- Security testing
- Browser compatibility testing
- Load / stress testing
- Interoperability testing/intersystem testing
- Storage and data volume testing

A web-application is a three-tier application.
This has a browser (monitors data) [monitoring is done using html, dhtml, xml, javascript]-> webserver (manipulates data) [manipulations are done using programming languages or scripts like adv java, asp, jsp, vbscript, javascript, perl, coldfusion, php] -> database server (stores data) [data storage and retrieval is done using databases like oracle, sql server, sybase, mysql].

The types of tests, which can be applied on this type of applications, are:
1. User interface testing for validation & user friendliness
2. Functionality testing to validate behaviors, i/p, error handling, o/p, manipulations, services levels, order of functionality, links, content of web page & backend coverage’s
3. Security testing
4. Browser compatibility
5. Load / stress testing
6. Interoperability testing
7. Storage & data volume testing

A client-server application is a two tier application.
This has forms & reporting at front-end (monitoring & manipulations are done) [using vb, vc++, core java, c, c++, d2k, power builder etc.,] -> database server at the backend [data storage & retrieval) [using ms access, sql server, oracle, sybase, mysql, quadbase etc.,]

The tests performed on these applications would be
1. User interface testing
2. Manual support testing
3. Functionality testing
4. Compatibility testing
5. Intersystem testing
Some more points to clear the difference between client server, web and desktop applications:

Desktop application:
1. Application runs in single memory (Front end and Back end in one place)
2. Single user only

Client/Server application:
1. Application runs in two or more machines
2. Application is a menu-driven
3. Connected mode (connection exists always until logout)
4. Limited number of users
5. Less number of network issues when compared to web app.

Web application:
1. Application runs in two or more machines
2. URL-driven
3. Disconnected mode (state less)
4. Unlimited number of users
5. Many issues like hardware compatibility, browser compatibility, version compatibility, security issues, performance issues etc.

As per difference in both the applications come where, how to access the resources. In client server once connection is made it will be in state on connected, whereas in case of web testing http protocol is stateless, then there comes logic of cookies, which is not in client server.

For client server application users are well known, whereas for web application any user can login and access the content, he/she will use it as per his intentions.

So, there are always issues of security and compatibility for web application.

Over to you: On which application are you working? Desktop, client-server or web application? What is your experience while testing these applications?

To get software testing articles in your inbox click here to subscribe with your email address. 

---------------------
I just wanted to thank you for subscribing to SoftwareTestingHelp.com. This blog is a success because of you and your support. Here's to your success!

As always, I appreciate your valuable comments. Visit below link to post your comment:
What is client-server and web based testing and how to test these applications

Thank you so much! ---------------------
Recommended: TestLodge - Online test case management tool - Web based test case management software allowing you to manage your test plans, requirements, test cases and test runs with ease.