Manual Testing Very Important Questions and Answers

Chapter 1
Testing Fundamentals
1. How do you define testing?

Testing is the process of finding/identifying the defects in order

1. to enhance product quality and

2. To enhance customer satisfaction.

2. Difference between testing and quality?

Quality can be thought of as an overall term, as the quality of the software product is
dependent upon many factors. In general, quality s/w should be reasonably bugfree, delivered
on time and within the original budget.

Testing is the measurement of software quality .We measure the achieved quality by testing
the relevant factors such as reliability, usability, maintainability etc.

3. Tell Top 3 reasons to convince CEO for testing?

 This question was asked to check whether you can think and act based on the situation.
Your CEO is business person, not a core technical person .He would like your words if
you speak from business benefits than technical .you can answer as follows

Testing is very essential for the growth of our organization since

1.Testing enhances customer satisfaction there by business benefits in the long run

2. Testing helps to save the reputation of the organization.

3. Testing reduces maintenance cost and gives great ROI (Returns On Investment).

4. Is testing constructive or destructive?

Testing is constructive through the approach of destruction. Testing process tries to

destruct or break the system to reveal the possible flaws in the system there by they can be
corrected before the product is released to the customer.

5. Why does software need to be tested?

Every software product needs to be tested since

1. The development process is not able to produce the defect free software.

2. Even if the development process is able to produce the defect free software, We will
not be able to know unless until we test it.

3. Without testing, we shall not be having enough confidence that product will work.

1
 Manual Testing Very Important Questions and Answers

4. Testingnot only identifies defects and reports defects but also measures the quality of
the product, which helps to decide whether to release the product or not.

6. Why software have bugs?

Here is the broad list of factors contributing to the presence of bugs in the software
applications

1. To err is human .Programmers like anyone else, can make mistakes

2. Miscommunication about specifications of what an application should or what an

application should not do.

3. Frequent requirement changes requested by customer leads to error due to last

minute design changes.

4. Software development tools like visual tools, class libraries, compilers, scripting tools
etc. often introduce their own bugs resulting in added bugs.

5. Quickly written code but poorly documented code is bound to have bugs. It becomes
difficult to maintain such code and modify such code

6. When the project deadlines come too close and time pressures come, mistakes are
bound to come.

7. Can you deliver the bug free product with testing?

No one can guarantee the bug free product through testing. Testing helps to release the
reasonably bug free product

8. If you cannot deliver the bug free product, then what is the use of testing?

Even though testing does not guarantee bug free product, it will help to find as many
bugs as and correct as many bugs as possible before the product reaches the customer.
Because of the bugs found through testing following benefits can be availed

1. Testing enhances customer satisfaction

2. Testing reduces the maintenance cost
3. Testing avoid critical errors like production server failures, data base corruption
issues, which would cause millions of dollars loss in case they occur
4. Testing can save the organization reputation.

9. What are the challenges of a test engineer?

Below are some of the challenges of a test engineer

a. Communicating effectively with developer to convey the defect information

b. Dealing with impacts that cause on the stable modules because of the changes in
the other functionalities

2
 Manual Testing Very Important Questions and Answers

c. Handling shortage of times for testing because of build delays

d. Building relationships with developers
e. Effective understanding and testing of complex applications from business point
of view.

12. What is bottom up integration testing?

Bottom up integration is an incremental integration testing technique, which begins by

developing the bottom level module first and testing the bottom level modules first and
progressively adding the top level modules one by one and testing the top level model one by
one. Top level modules are normally simulated by drivers.

13. What is the driver?

Driver is the code, which calls other functions. Driver checks whether the function is
developed correctly or not based on the return value.

14. Give example of driver?

Below driver code calls the function getinterestamount and checks the its return value.

Intrstamount= getinterestamount(1000,12,6)

If (Intrstamount=60)

Printf(“ get interestamount function is working fine”)

Else

Printf(“ get interestamount function is not working fine”)

15. What is an early integration?

Early integration is nothing but testing a module in a project much before the actual
release of the module. This is done with the help of integration techniques like top down,
bottom up, sandwich integration.

16. Have you involved in writing stubs and drivers?

3
 Manual Testing Very Important Questions and Answers

I have a good idea on what stub and driver are and how to implement them. However I
have not got any opportunity to write stubs and drivers because the component integration
was handled by the development team in my earlier projects .In case if I am supposed to write
stubs or drivers in current project ,I am confident that I can handle it

17. What is system testing?

System testing is defined as the process of testing an entire system to verify that it
meets the specified requirements.

System testing is of two types

1. Functional system testing.

2. Nonfunctional system testing.

18. What is difference between the functional and nonfunctional system testing?

Functional system testing is nothing but testing the system based on its functional
behavior.

Nonfunctional system testing is nothing but testing the system based on all other aspects,
except its functional behavior.

19. What are types of functional testing?

Functional testing consists of 2 types

1. Requirements based functional testing:

Requirements based functional testing focus on testing the functionality of each use case on
screen .For requirements based functional testing; we identify test conditions and prepare test
cases.

2. Business process based functional testing:

Business process based functional testing focuses on testing application from business point of
view. For business process flow based functional testing, we develop test procedures by
identifying the business workflows. Test procedure is a set of test cases in executed in a
particular order

20. What are nonfunctional testing’s?

Some examples of nonfunctional testing’s.

1. Performance testing
2. Browser compatibility testing
3. Installation testing
4. Penetration/security testing.

4
 Manual Testing Very Important Questions and Answers

21 what is performance testing?

Performance testing used to test the response time of the system for a different user
loads. Under performance testing umbrella various types of testing can be conducted

Like load testing, stress testing, volume testing, endurance test/soak test, spike test

Load testing: To determine the scalability of the application under the real world scenarios.

Stress testing: To determine the breaking point of server.

Volume testing: To test the performance of the application at high volumes of data.

Endurance test/soak test: To determine the stability of the application by executing the load
test for an extended period of time and finding out the memory bottleneck s

Spike test: To determine the impact on the application of a sudden increase/ spike in load
during abnormal conditions

22. How do you conduct volume testing for a project which has 5 million users data base?

Creating 5 million user entries manually is very tough task and timing consuming task.
Instead I write an SQL procedure which creates this data for me.

23. What is installation testing?

Installation testing is used to test whether the installation, uninstallation, reinstallation

and upgradation of the product is happening properly.

It is very important to make sure that customers do not have any trouble in installing the
software since it is the first interaction of the customer with our product.

24 How will you plan installation testing?

The approach of testing we do, will be affected by lots of factor like

1. What platforms and what operating systems you support?

2. How will you distribute the software?

=>what platforms and operating systems you support?

Follow below guide line to conduct the installation testing of all platforms

a. Create a tree structure of all the options available to the user and cover all unique paths
of installation if possible and cover all the paths.
Example tree structure is

5
 Manual Testing Very Important Questions and Answers

Platform

Unix windows MAC

GUI CLI GUI

CLI
Fresh Reinstallation Upgradation Repair
installation

B.Write test cases for following

1. To check the file system registry, DLL etc. are created properly. You can also use some
tools to perform this check.
2. In case of silent installation, check any changes made to the config file is having proper
effect on the installation
3. Test negative cases like insufficient memory, insufficient space and aborted installation

=> How will you distribute the software?

If the software is distributed using physical CD format, test activities should include following
things

1. Test cases should be executed from ISO images, if getting physical CD is not possible.
2. Test cases should be present to check the sequence of CD’s used.
3. Test cases should be present for the gracefully handling of corrupted CD or image

If test cases are distributed from internet, test cases should be included for

1. Bad network speed and broken connection.

2. Firewall and security related
3. Size and approximate time taken.
4. concurrent installation / downloads

25. Difference between ad-hoc and exploratory testing?

Ad-hoc testing means testing the application without following any test cases.

Exploratory testing is an approach of testing an application which involves simultaneous

learning, test design and test execution.

6
 Manual Testing Very Important Questions and Answers

Exploratory testing is a style of software testing that emphasizes the personal freedom and
responsibility of the individual tester to continually optimize the quality of his/her work by
treating test related learning, test design, test execution and test result interpretation as
mutually supportive activities that run in parallel throughout the project.

26. What is mutation testing, monkey testing and random testing?

Mutation testing is used to test the effectiveness of test cases. This is a method of
software testing, which involves modifying program’s source code in small ways and running
tests to check their effectiveness to catch the defects.
Monkey testing is nothing but entering random strings into text boxes. A monkey runs with no
specific test in mind. The monkey in this case is the producer of any input.

Random testing is nothing but testing the application modules/fields randomly. Random testing
is also known as Gorilla testing.

27. What is penetration testing?

Penetration testing, occasionally pen test, is a method of evaluating the security of a

computer system or network by simulating an attack from malicious source also known as
security testing.

28. What is localization and internationalization testing?

Internationalization testing is the process of testing whether software applications can be

adapted to various languages and regions .This is also called as I18N (I-eighteen-N) testing since
there are 18 characters between I and N.

Localization testing is the process of testing whether the software has been adapted correctly
for a specific language. This is also called L10N (L –TEN- N) testing since there are 10 characters
between L and N.

29. What is globalization testing?

Some companies, like IBM understand Sun Micro Systems; use the term “globalization”
for the combination of internationalization and localization. Globalization can also be
abbreviated to G11N.

30. How system testing and system integration testing differ?

System testing is the functional and nonfunctional testing of the project.

System integration testing is concerned with ensuring interactions between two or more
systems.

31. I prefer to conduct system testing directly by avoiding component and integration testing.
Do you agree with me?

7
 Manual Testing Very Important Questions and Answers

Component testing is the testing conducted by developer to ensure that his developed
components are working. This cannot be avoided, because if any developer gives code without
component testing, it will have lots of defects and waste lots time for reporting, fixing and
verifying defects. Even though with the help of system testing, we can prove overall system is
functioning. It may not give that thorough focus for data transfer or interaction between
components. Hence I feel all the levels of testing are essential for better stability and reliability
of the product.

32. What are the types of acceptance testing?

Following 3 types are considered as acceptance testing types.

1. Alpha testing
2. Beta testing
3. User acceptance testing

33. What is Alpha testing?

Alpha testing is the testing conducted by the customer in engineering premises.

34. What is beta testing?

Beta testing is the testing conducted by end user in production environment.

35. How Alpha and beta testing differ?

Alpha testing is performed by the customer in engineering premises, whereas beta
testing is performed by end user in the production/ live environment.

36. What is user acceptance testing?

User acceptance testing is the final testing conducted by the customer before formally
accepting the product.

1. Customers may choose to do any test they wish, normally based on their usual business
processes.
2. A common approach is to set up a model office where the systems are tested in an
environment as close to field use as is achievable.

37. Successful beta testing means end user is happy with the product. In such instance, why
do we require user acceptance testing?

During beta testing, application is tested only from end user point of view. For example
in banking application, during beta testing end user might test transfer functionality by
transferring the payment to another account.But many other activities related to transfer like,
whether transfer details are recorded in daily transaction details of ATM, bank global records
etc. cannot be verified by end user. Moreover any documentation related to project like user
manual may not be available during beta testing. One more thing that may not be possible to

8
 Manual Testing Very Important Questions and Answers

test always during beta testing is the performance of the application .Hence acceptance testing
is very essential go to the through the entire product and accept formally before the project is
signed off.

38. What is your involvement in user acceptance testing?

I have involved in setting up the test environment for running acceptance tests and I
also involved in verifying the bugs fixed during acceptance testing.

39.Who writes acceptance test plan and acceptance test cases?

Acceptance test plan and acceptance test cases should be written by customer
immediately after requirements are free zed. However these should be approved by delivery
manager. Usually there will be a review meeting between the customer, business analysts,
development manager, test manager and delivery manager for formal approval of the
acceptance test cases.

40. What is smoke testing?

Smoke testing is the testing conducted to check whether the basic functionality is
correctly working in a given build.
This is conducted to verify whether the build is good enough to consider for further detailed
testing. This is the first test conducted before the build is considered for detailed testing. This is
also known as BVT (build verification test)

41. Why is smoke testing is essential?

Testing believes that testing a product which is not meeting certain basic functional
requirements is a waste of time and it does not result good quality of the software. So in order
to ensure that build is meeting basic functionality goals before further detailed testing, We
conduct smoke testing.

42. Why build will be released without basic functionality?

2 reasons

1. While creating the build, build process uses lots of external libraries. If you any one of
these libraries are not linked correctly, then bill will not be generated.

2. In experienced developer developed the code of a particular module resulting

completely not functional module.

43. Why smoke test is called as smoke test?

In electronics industry after circuit board is ready, technicians used to give me a small
voltage to test whether the board has any short circuits . If there is any short circuit, smoke will
come from the board, else they give full voltage to test the board. Since they were checking for
the smoke from the board it was called smoke test . Similarly for the software also we are using
basic tests to check whether build is correctly created before we go for detailed testing, Hence
we are also using the word smoke test.

9
 Manual Testing Very Important Questions and Answers

44. How do you identify smoke tests? And who will do that in our project?
Smoke tests are basic tests for verifying whether the build is created successfully. Smoke
test involves common activities like

1. opening URL of the application

2. Logging into the application
3. Verifying whether the important links are present and they are opening the
corresponding pages.
Smoke tests are identified by senior test engineers for their respective models along
with test lead. Test Lead also takes approval from development team before base lining
smoke test cases.

45. After receiving build, what will you do?

First thing we do after receiving the build is running the smoke test cases.

46. Until smoke test cases are completed what are the rest of the team will do?
One of our team members ,who is responsible for smoke test case execution reach the
office early during the build release and complete the smoke testing and sends smoke testing
successful e-mail before everyone reaches office .

(Or)
We have an automated smoke test suite which will be executed for every build. These
automated tests take hardly 25 to 30 minutes. These will be executed by one of our team
member by reaching the office bit early during build release dates.

47. Do you report defect if smoke test fails?

No .Entire build is rejected. We accept next build for detailed testing, only when smoke
tests are successful. So there is no need to track this failure separately. Hence defect will not be
reported.

48. Difference between smoke testing and sanity testing?

There is a difference in the opinion among testing teams related to smoke and sanity.
Few consider smoke is breadth wise testing and sanity is the depth wise testing. I mean smoke
tests all the functionalities of the build at a surface level where as Sanity focuses on deep
testing of given functionality. Others consider sanity is an alternative term for smoke testing.
In our organization, we only use the terminology called smoke testing for build verification
before proceeding for detail functional testing .

49. What is regression testing?

Regression testing is the testing connected to check whether unchanged functionalities

10
 Manual Testing Very Important Questions and Answers

have got any side effect due to changed functionalities.

It is performed whenever the software or test environment is changed.

50. How do you select regression test cases?

We select regression test cases by calculating risk exposure factor of each test case.

Risk exposure factor (RE)=P*C

Where RE is the risk exposure factor of a test case

P is the probability of a fault occurring in test cases

C is the cost of fault is executed in test case.

Risk based test case selection:

Step 1: estimate the cost for each test case

Cost is categorized on a one to 5 scale (one is low ,5 is high) based on the consequences
of a fault as seen by the customer. For example, losing market share because of faults.

Step 2: Derive severity probability for each test case

For each test case, we compute severity probability depending on the number of defects and
severity of defects. Severity probability falls into a 0 to 5 scale, where 0 is low and 5 is high

Step 3: Calculate risk exposure for each test case

risk exposure is the multiplication of cost and severity probability.

Step 4: Select test cases that have the highest value of risk exposure.

51. Who identifies regression test cases?

Senior test engineer along with Test Lead will identify regression test cases.

52. How do you decide the amount of regression testing required for the project?
The amount of regression testing required is based on the impact of changes on other
modules. If time is sufficient, we try to run the full regression, else we try to run the regression
tests based on the identified impacted areas. It is always a good practice to have an automated
regression suite for quick and effective regression coverage.

11
 Manual Testing Very Important Questions and Answers

53. What is the difference between test types and test levels?
Test levels indicates the level at which we are testing the product like a component or
between components or entire a system. Test types indicate whether testing is a functional or
nonfunctional or structural. In a particular level of testing you can have multiple test types. For
example system testing level has both functional and nonfunctional system testing.

54. What is the difference between testing techniques and testing types?
Testing techniques refers to white box or black box testing where as testing type refers
functional or nonfunctional.

********************end of chapter -1 Testing Fundamentals*************************

Chapter 4

Software Development Life Cycle

1. What is software life cycle?
The life cycle begins when an application is first started and ends when it is no longer in use. It
includes aspects such as requirements analysis, design, coding, testing and maintenance.

2. What is the waterfall development method?

In a typical model, a project begins with feasibility analysis. On successfully demonstrating the
feasibility of a project, the requirement analysis and project planning begins. Design starts after
requirement analysis is complete. Coding begins after the design is completed .once the
programming is completed, the code is integrated and testing is done. On successful
completion of testing, the system is installed. After this, the regular operation and maintenance
of the system takes place.

3. What are the advantages and disadvantages of waterfall model?

Advantages:

1. Waterfall is a linear model. Hence it is simple to understand and follow.

2. Good for small projects with freezed requirements

Disadvantages:

1. Waterfall model cannot adapt to changes in the requirements.

2. Testing starts only after development. The quality of product is the concern for large
projects.

4. What is prototyping model of software developing?

12
 Manual Testing Very Important Questions and Answers

A Prototype is a toy implementation of a system .Usually exhibiting limited functional

capabilities, low reliability and inefficient performance. There are several reasons for
developing a prototype. An important purpose is to illustrate the input data formats, messages,
reports and the interactive dialogues the customer .This is a valuable mechanism for gaining
better understanding of the customer’s needs . Another important use of the prototyping
model is that it helps critically examine the technical issues associated with the product
development.

5. Explain V- model?
The V-model demonstrates the relationships between each phase of the development life cycle
and it’s associated the phase of testing. V-model consists of a number of phases. The
development phases are on the left hand side of the V. The coding phase is at the bottom of the
V and the validation phases are on the right side of the V.
1.Requirements analysis:

In this phase software requirements specification is developed by interacting with

customer. As part of validation during this phase, acceptance test plan will be prepared this is
used during user acceptance testing. This acceptance test plan contains all the tests required to
verify whether the software is meeting all requirements mentioned in the software
requirements specification .
2. System design / high level design:
System design is also known as high level design. Development team prepares a document with
all the modules system contains and also the features supported by each module. As part of
validation, system test plan will be prepared which contains information about all the
functional and nonfunctional tests required to test the entire system developed.

3. Low level design:

The low level design document or program specifications will contain a detailed functional logic
of the module, pseudo code. As a part of validation, integration test plan will be prepared to
test the low level design of the system.

4. CUT phase:

this is called as coding and unit testing phase . In this phase unit test plan and test are
prepared to test each function program being developed.

6. Advantages and disadvantages of v model?

Advantages:

1. Emphasis is given for testing at each phase of development.

2. Hence applications developed through this model are usually more stable.

Disadvantages:

13
 Manual Testing Very Important Questions and Answers

1. V-Model is good only for large projects and also with free zed requirements.
2. It needs lot of resources and money. It needs an established the process to implement.

7. Your manager feels V- model is vast and unnecessary because it has lots of documentation
involved. Do you agree?

My manager is very experienced and he will not come out with such opinion until there is a
strong reason behind it. I agree with him in case project is small and waterfall model is
sufficient to develop this project. Incase project is large and has a frozen requirements i would
share my opinion with my manager stating that V- model has strong integration with each
phase of development and it gives very early focus on the testing activities of the project .

8. Explain agile methodology?

Agile software development refers to a group of software development methodologies based

on iterative development ..

agile methodology principles are :

1. Individuals and interactions over processes and tools .

2. working software over comprehensive documentation .
3. Customer collaboration over contract negotiation.
4. Responding to change over following plan.

Scrum is an iterative incremental framework for agile software development .

Diagram :

14
 Manual Testing Very Important Questions and Answers

The sprint cycle is an iterative cycle of about 3 to 4 weeks, in which the actual development of
the product is done . It starts out with sprint planning meeting to decide what will be done in
the current sprint. Then the development is done.A sprint is closed with sprint review meeting
where the progress made in the last sprint is demonstrated,the sprint is reviewed and
adjustments are made to the project as necessary .

Scrum meetings:
Daily scrum meeting:

A 15 minute scrum meeting is held every day. The scrum master asks 3 questions and all
members of the team and interested parties take part and give feedback. The meeting should
be held at the same place every time, so that people know where to go.
3 questions
The scrum master 3 important questions at every scrum meeting.
1. What have you accomplished since the last meeting?

2. Are there any obstacles in the way of meeting your goal?

3. What will you accomplish before the next meeting?

Sprint planning meeting :

A meeting at the beginning of a sprint where the sprint is planned. Item from the product
backlog are selected to be completed in the sprint, based on the priorities set by the product
owner.

Sprint review meeting :

A Sprint is closed with a sprint review meeting, where the progress made in the last sprint
is demonstrated, the sprint is reviewed, and adjustments are made to the project as necessary.

Scrum of scrums:

Each day normally after the daily scrum. These meeting allow clusters of teams to discuss
their work, focusing especially on areas of overlap and integration. A designated person from
each team attends.

15
 Manual Testing Very Important Questions and Answers

9. What are the advantages and disadvantages of Agile methodology?

Advantages of methodology:

1. Agile methodology has an adaptive team which is able to respond to the changing
requirements.
2. The team does not have to invest time and effort and finally find that by the time they
deliver the product, the requirement of the customer has changed.
3. Face to face communication and continuous inputs from customer representative
leaves no space for guess work .
4. The documentation is crisp and to the point to save time
5. The end result is high quality software in least possible time duration and satisfied
customer .
Disadvantages of agile methodology:

1. In case of some software deliverables, especially the large ones, it is difficult to assess
the effort required at the beginning of the software development life cycle.
2. There is lack of emphasis on necessary designing and documentation.
3. The project can easily get taken off track, if the customer representative is not clear
what final outcome that they want.
4. Only senior programmer are capable of taking the kind of decisions required during the
development process .Hence it has no place for newbie programmers, unless combined
with experience resources

10. You are supposed to recommend the best SDLC model for your project? How will you do
this?
All SDLC models have their strengths and weakness. To decide which SDLC model is best for my
project. I have to look at various parameters of the project like complexity, requirements are
frozen or not. Small projects with frozen requirements, I would recommend waterfall model,
large project with frozen requirements, I would recommend V-model, project without frozen
requirement i would recommend incremental iterative models like agile methodology .

11. What is test driven development?

This is the development model where the development is driven by testing. In this model,
test cases are developed before coding and developers develop the code which will pass all
those test cases.

12. What is Pair programming?

Pair programming is one of the software development methodologies where two people sit
and do the programming. One programmer develops the code another one analyzes the code
for the effectiveness of logic adherence to coding standards and syntax errors. Idea is if 2
people sit together and code , the code is very effective and is of good quality .

16
 Manual Testing Very Important Questions and Answers

though initial response was good for this methodology ,it is not that much successful due to
issues among the pair participated in extreme programming . Some of the issues observed were
time adjustment, prolonged arguments

****** end of Chapter 4- SDLC ************** ****************************

Chapter 5
Maintenance Phase

1. What is a maintenance phase?

Maintenance phase is nothing but the phase of the project after the release .

2. What are the alternative names of maintenance phase?

1. Production phase
2. Post release phase
3. Live environment
4. Customer environment

3. What is the importance of maintenance phase?

Maintenance phase is very important and because

1. Once project is in live any critical defects will have a severe impact on the business. Hence they
require an immediate solution which is carried out by maintenance team.
2. Legal laws and business plans may be changing time to time, which may demand some more
changes to the software in the current project. This requires maintenance of the software.

4. Why defects arise in the maintenance phase even after testing?

Even though project is well tested, no one can guarantee defect free release. Some defects will be
identified because of

1. The specific way project is used in the business which is not identified during testing.
2. Changes in the software and hardware.
3. Changes in the test data.

5. Which activities are usually carried out in the maintenance phase?

1. Providing hot fixes

2. releasing patches
3. Releasing service packs

17
 Manual Testing Very Important Questions and Answers

6. What is hot fix?

Hot fix is a critical bug identified in production environment that requires an immediate fix else business
cannot continue. These kinds of issues are fixed and released immediately to customer.

7. What is a patch?
Patch is small software that contains fixes for one or more bugs identified in the application. Patches are
related to the customer by the vendor of the software, with solutions for the issues identified in the
product during its maintenance.

8. What is a service pack?

Service pack contains code changes of all the patches released before this services pack. Service Pack is
also called as maintenance update. This is released for the maintenance of software. Usually service
pack is released once in 6 months.

9. What are the activities of a test engineer in maintenance phase?

Maintenance activity Types of testing conducted

Hot fix  Bug verification

 Regression testing
 Hot fix installation

Patches  Bug verification

 Regression testing
 Functional testing (optional )
Service pack  Bug verification(only to bugs fixed in this
service pack)
 Regression testing
 Functional testing (only to changed
requirements and new features)
 performance testing
 service pack installation testing

10. If there is a hot fix, developer will be working on fixing the same. As a tester what are your
activities during this time ?
As a test engineer I have to verify the hot fix and I also should conduct regression testing for the same.
Since time is very critical for hot fix. I would prefer to do possible testing activities in parallel to
development so that time to release can be reduced.
Activities I do and time at which I do are:

18
 Manual Testing Very Important Questions and Answers

Activities of Tester Time frame

1. Understand defect (hot fix)
2. Think about any possible work around .
3. Reproduce the hot fix.
4. Identify test conditions and prepare for
additional tests if required.
1. Setup test environment like OS (operating During Fix
system) and other related software

1. Re-test the bug After fix

2. Regress the application.

11. How long maintenance phase will be there?

Usually 8- 10 times of the deployment duration. This means if your project development takes 1 year
maintenance takes around 10 years .

12. What is EOL?

EOL means end of life of product. This means after the EOL, no support will be provided for the bugs
reported by the customer. In other words maintenance phase of the released project is completed.

13. How much effort is required during maintenance phase?

Maintenance phase effort will be approximately 1.5 times of Pre-release effort.

14. How much budget will be spent on testing ?

Budget also approximately 1.5 times of the Pre-release. Difference is what ever be the budget spent
during the prerelease in a year time: same will be spent in around 10 years during the maintenance
phase.

15. How testing saves maintenance cost?

If the project is well tested, number of defects identified in maintenance phase will be less. Hence effort
to be invested to solve customer issue is less. Less effort means less budget and less cost. So by having
an effective testing before releasing the project. We can reduce the effect involved in maintenance
phase and hence save the cost.

********************end of Chapt 5-Maintenance phase

Chapter 6
Software Test Life Cycle

19
 Manual Testing Very Important Questions and Answers

1. Explain the test process or test life cycle you follow ?

We follow testing life cycle as shown below

Requirement study

Test planning

Test case design

Test data selection

Test case execution and

defect reporting

Regression and retesting

Testing exit analysis

Test closure

2. What is entry criteria?

Entry criteria define what should be there before we start a particular phase.

3. What is an exit criteria?

Exit criteria defines what should be there to tell we have successfully completed a particular
phase.

20
 Manual Testing Very Important Questions and Answers

4. Explain entry and exit criteria for each phase of test life cycle?

Phase Entry criteria Exit criteria

Requirements study 1. Base lined SRS Understanding requirements

2. Base lined BRS
1. Base lined SRS Base lined test plan
Test planning 2. Base lined BRS
test case design and test data 1. Base lined SRS 1. Identification of test
selection 2. Base lined test plan scenarios/test
conditions
2. Identification of test
data
3. Base line test cases
4. Base lined test
procedures/work
flows
Test execution& Reporting 1. Base lined test cases 1. Preparing test
defects 2. Base lined test execution reports
procedures 2. Logging defects
3. Test environments
availability
Regression & re-testing  Base lined regression 1. Regression tests
test cases execution
2. Verifying fixed defects
Test exit analysis 1. Test coverage reports 1. Preparing test
2. Bug reports summary reports
3. RTM 2. Taking decision to
stop or continue
testing
Test closure activities  Decision to stop 1. Checking whether
testing planned deliverables
have been delivered
2. Finalizing and
archiving testware
3. Handover of testware
for maintenance
4. Analyzing lessons
learned for
improvement of test
maturity
5. Testing sign off
*********************** Chapter 6 STLC
****************************************************

21
 Manual Testing Very Important Questions and Answers

Chapter 7
Software Requirements
1. How will you receive project requirements?
Finalized SRS will be placed in a project repository. We will be accessing from there.

2. What will you do with SRS?

We use SRS document to understand the project functionalities from business and functional point
of view .

3. Does testing team involve in SRS preparation?

Business analysts prepare this document by interacting with customer. However senior testing team
member can also involve in requirements collection along with development team and business
analysts team.

4. How your requirements document looks like?

It contains lots of use cases where each case explaining one or more functionalities.

5. How will you understand the requirements?

If this is known domain by going through usecases I can understand the requirements. If I have some
queries, I will discuss with business analysts for clarifications. If it is a new domain, first I will get
domain training, then I go through the usecases. If the project requirements are very confusing,
then business analyst can also walked through each use case.

6. How do you understand functionality without screen?

We get white frames in the usecases , which helps a lot to understand the functionality.

7. What is white frame?

A diagram which simulates the feel of actual screen.

8. What is use case?

Use case is a document that explains purpose and use of a particular functionality in the way end user
use this functionality in the business. Usecase documents each step performed by user in a detailed
manner in the form of normal flow, additional flow, and exceptional flow.

9. What do you mean by detailed manner?

Each usecase contains lots of section such as objective, actors, precondition, normal course, additional
course and exceptional course.

1. Normal course explains a general usage of the functionality step by step.

22
 Manual Testing Very Important Questions and Answers

2. Additional course explains additional activities an end user can perform.

3. Exceptional course explains general error or information messages thrown by the system.

10. Did you involve in writing usecases?

I am aware of how use cases looks like and I can write if required. But I have never got an opportunity
to write use cases because these are prepared by requirements gathering team. Anyhow I have
reviewed use cases of certain functionalities and have given my inputs for the development of the
same.

11. Can you tell different sections present in SRS document ?

1. Overview
2. Scope
3. Features
4. User characteristics
5. Software requirements
6. Hardware requirements
7. Performance requirements
8. Security and reliability requirements
9. Use cases.

12. How long do you spend on understanding the SRS document?

It depends on the familiarity of the domain and the complexity of the project. If familiar domain, we can
understand about 25 pages of documentation every day. For a new or complex domain around 15 pages
per day.

13. After understanding SRS, what do you do?

My lead asks for a presentation of the functionalities I am assigned with. If I am in a position to explain
the functionalities clearly to the team, then I am considered as a comfortable with the functionality.

14 .Should you understand the whole project functionality, only the functionality assigned to you?

I should have a big picture of the whole project, other words over view of the whole project and detailed
screen and field level understanding of the assigned functionalities.

15. What are the different models generally followed in the documenting requirements?

2 models are followed in documenting the requirement which is use case model and paragraph model.
In Paragraph model, business requirements are written like a paragraph which is old model. Now a days
almost all the companies are following use case model where the requirements are written by stating
their clear objectives and explained with the help of screenshots.

23
 Manual Testing Very Important Questions and Answers

16. Have you contributed to SRS any time?

In the project HR one team there was no remarks…. To see why the profile was rejected. I have
proposed is enhancement and everyone have agreed and included in SRS.

17. How big is your SRS document?

Note : you can answer anything like approximately 250 pages .this question is asked to cross check
whether you have seen SRS or not.

18. What will be the problem Without SRS document?

Without SRS document we are not able to understand the project features correctly. Hence we will not
be able to test the project in depth and deliver the business quality products.

19. What is a BRS document?

BRS is a business requirements specification which is usually prepared before preparing an SRS
document. This document gives a high level view of what is being required by the customer to meet
business needs.

20. What is the technical requirements specification?

This is also called as a high level design,which consists of different modules present in the
project.

***************End of Chapter 7- Software Requirements***************

Chapter 8

Reviews
1. What is review?

Review is a meeting in which a work product, which can be any document in the project, can
be verified by set of members.

2. Explain the review process you follow in your organization?

The various phases of the review process followed in my organization are:

1. Planning
2. Kick off
3. Individual preparation
4. Review meeting
5. Re work

24
 Manual Testing Very Important Questions and Answers

6. Follow up

Planning:

This phase involves

1. Selecting thepersonnel for review.

2. Allocating roles.
3. Defining entry criteria and exit criteria.

Kickoff:

This phase involves

1. Distributing documents
2. Explain the objectives
3. Checking entry criteria etc.

Individual preparation:

In this phase, each of the Participants will work before the review meeting and be ready with
the questions and comments.

Review meeting:

This phase involves

1. Discussion among the review members by going through each line of the work
product or a document
2. Logging comments
3. Make decisions about the defects.

Rework:

This phase involves

 Fixing defects found during the review, typically done by the author.

Follow up:

This phase involves

1. Checking the defects that have been addressed

2. Gathering metrics and checking the exit criteria.

3. What are the roles present in the review?

Manager:

Manager is the person

25
 Manual Testing Very Important Questions and Answers

1. Who decides on execution of reviews?

2. Who allocates time in projects schedules?
3. Who determines if review objectives have been met?

Moderator:

Moderator is the person

1. Who leads the review, including planning, running the meeting?

2. Who follow up after the meeting?

Author:

Author is the person, who has created the item to be reviewed. The author may also be
asked questions with in the review.

Reviewer:

The reviewers are the attendees of the review who are attempting to find error in the
item under review. This should come from different perspectives in order to provide a
well-balanced review of the item.

Scribe:

Scribe or recorder is the person, who is responsible for documenting issues raised
during the process of the review meeting.

4. What is the peer review?

Peer review is a review of software work product by colleagues.

Examples are inspection, technical review and walkthrough.

5. What is the difference between the walkthrough, technical review, inspection?

Walkthrough Technical review Inspection

Meeting is led by the author Technical review ideally led by Inspection is led by trained
trained moderator moderator but not the
author.

goal is to quickly check the Inspection goal is to formally

quality of work Technical review goal is to approve the work.
find best out of multiple
designs and logics.

In walkthrough, the author In technical review, as a team The author must implement

26
 Manual Testing Very Important Questions and Answers

may or may not implement all identify the best solution for the agreed comments of
suggestions of review team the problem reviewers before formally
members. Leave the accepting the product.
suggestions as open.

In walkthrough team will In technical review, team will In Inspection team will involve
involve in review. involve in the review. in review.

In walkthrough vary in In technical review, vary in Inspection is very formal.

practice from quite informal practice from quite informal
to very formal. to very formal.

findings may or may not be Findings will be documented.

documented.
Findings may or may not be
documented .
Checklists will not be there. Optionally can have check Often have a checklist.
lists.

6. What is the difference between static and dynamic testing?

Static testing means testing the project without executing the software.

Dynamic testing means testing the project by executing the software i.e. running the
application and going through screens. to conduct dynamic testing, you must use the
application screens and enter valid input and invalid inputs and verify the application behavior.

For static testing, we do not use any screens of application, instead we use static techniques
like review. During review, experts go through each line of the work products like requirements
document, design document and identify mistakes in these documents. Any mistakes identified
during the review are nothing but defects in the work product.

7. I want you to choose one among static and dynamic testing for the project?Which one you
choose and why?

Static testing reduces the cost of fix and dynamic testing gives the complete confidence to
release the product. According to me both are equally important and both of them contribute
equally for the project success. So I prefer to have both. However, if I have to choose one I
choose dynamic testing since I cannot let the project release until I see with my eyes that it is
working.

8. Out of formal and informal review which one you prefer?

In my view, both are important. Informal review is very fast and formal review is effective.

27
 Manual Testing Very Important Questions and Answers

We have to use both depending on the data we are reviewing. I prefer formal and informal
review techniques as follows.

Formal review:

1. Reviewing test case document created

2. Reviewing test plan document created
3. reviewing test scripts developed

Informal review:

1. Reviewing tests used for retesting.

2. Reviewing minor changes in test case, test plan or test scripts.

9. How do you decide the review outcome?

Review outcome is decided by moderator. I can share my views with him. For example in test
cases review, outcome decision is as follows

Observation Outcome

a. Most of the critical test cases are Reject and redo work product.
missed.
b. Documentation standards are poor.

Major changes are suggested. Accept after correction with another round of
review.

Minor changes aresuggested. Accept after correction without another round of

review.
Accept as it is.
No changes suggested.

10. What kind of bugs can you find during static testing?

The following kind of bugs can be found in static testing.

1. Efficiency of logic
2. Memory leaks
3. Un-reachable code
4. Variables that are never used
5. Programming standard violations

11. Can you give an example of unreachable code?

28
 Manual Testing Very Important Questions and Answers

Example:

age=25

if age <18 then

------------

------------

End if

In the above code, if condition will never be reached.

12. Explain what do you document during review process?

Page and line number of defect, origin of defect, severity of defect. We also document other
information like work product id, reviewers etc.

13. How much information can you review in one day?

Perhour, we review around 30 pages, if it is documentation and 200 lines, if it is code.

However any review can go for maximum of two hours more than that review will not be
effective.

14. How do you say review was effective/successful?

If every reviewer prepares well before review and provide some good comments for
improvement of the work product, We can say review is successful.

15. What is a code review?

Code review is the process of reviewing the code written. Code reviews are conducted for the
code developed by developer and also for the automation scripts developed by the automation
engineer.

16. What is a desk check?

This is an informal review where colleagues come to the desk/ computer of the author and
quickly goes through the work product along with the author and also shares comments while
going through it.

************** end of Chapter 8 Reviews ******************************************

29
 Manual Testing Very Important Questions and Answers

Chapter 9

Test plan

1. What is test plan?

Test plan is a document that explains the approach for testing a project. It Describes the features to be
tested, out of scope, test strategy, schedule of testing activities, roles and responsibilities and any risks
requiring contingency planning.

2. When is test plan prepared?

A Test plan document should be prepared after the requirements of the project are confirmed.

3. What are the important sections of a test plan?

The important sections of test plan are

1. Test strategy
2. Features to be tested
3. Out of scope
4. Test deliverables
5. Risk and contingency

4. What is the importance of test plan?

Test plan document is the most important document that brings in a process oriented approach. From
test plan, we will find the information like

1. What features to test in the project?

2. Which part of testing is out of scope?
3. What kind of tests to be conducted?
4. What is test environment?
5. How we should communicate with developer and customers.
6. Milestone for different testing activities.

5. How many types of test plan can we have in a project?

1. Master test plan

2. System test plan
3. System integration test plan
4. Acceptance test plan

6. What is the difference between master test plan and system test plan?

Master test plan is written at the project level which consists of details like different levels of testing
conducted for the entire project and team responsible for each of these testing .Risks involved and
mitigation plans.

30
 Manual Testing Very Important Questions and Answers

System test plan focus on system testing of the particular application. Each application contains one
system test plan usually prepared by test lead of a system under test. System test plan contains
information like entry and exit criteria. Test environment details like hardware and software, procedure
test case management, defect logging etc.

7. Who prepares test plan?

Master test plan has to be prepared by the in charge of end to end testing like test manager.

System test plan has to be prepared by the in charge of testing a particular system/ application like a
test lead.

Component integration test plan has to be prepared by development team which is responsible for
integration of components developed by an individual developer.

System integration test plan has to be prepared by the team which is responsible for certifying
successful integration of the various systems/applications involved in the project. These different
systems involved integration can be of those newly developed or those which are existing or of COTS
systems. However all the system involved in system integration testing must complete their system
testing successfully.

Acceptance test plan should be prepared by a team which is responsible for UAT.Usually clients
outsource this to a company other than the company developing software.

8. Explain test deliverables?

Artifacts produced during the test process such as test plan, test conditions, test cases, and test
procedures. Test execution reports, test summary reports and automation scripts are known as test
deliverables.

9. Explain various testing's conducted in your project?

I worked on a web based e-commerce applications.So we have conducted following testing’s

1. Requirements based functional testing

2. Business process flow based functional testing
3. Browser compatibility testing
4. Performance testing
5. Security testing/penetration testing
6. Smoke testing
7. Regression testing

10. When do you stop testing for the given project?

We stop testing a project when

1. Traceability matrix shows that all the requirements are covered through testing.
2. Test coverage report is 100%
3. All the medium and above severity bugs are fixed, else they have differed with concurrence of
all stakeholders.

31
 Manual Testing Very Important Questions and Answers

11. What is a test exit criteria?

Same as above. Test exit Criteria can also be called as test stop Criteria.

12. What is the difference between suspension and stop criteria?

1. Suspension is halting the testing temporally with dissatisfaction because of situation like
failure of smoke tests.
2. Stop criteria is halting the testing with a satisfaction that product can be released.

13. What is traceability matrix and who develops it?

Traceability matrix also known as requirement traceability matrix (RTM).

This is used to ensure that each requirement has been covered as part of the testing. This means
ensuring each requirement has at least one corresponding test case.

If we are using quality center, this can be generated as requirements tab> analysis>Requirements
coverage report.

If we are not using quality Centre, it is prepared in excel file by module lead.

14. What is your contribution in test plan preparation?

Test plan is prepared by my manager. But I share views from my module point of view of certain
points to be included in the test plan. Few areas I share my views about my module are.

1. Anything to include in out of scope section.

2. Possible and preferred areas to automate.
3. Any specific type of testing required which is very specific to my module.

***************** end of chapter 9 Test plan *************************************

Chapter 10

Test design techniques

1. What are different categories of testing?

Two Categories of testing are there

1. Black box testing

2. White box testing

2. What is difference between white box testing and black box testing?

White box tests the application form code point of view and black box tests the application from
functionality point of view.

32
 Manual Testing Very Important Questions and Answers

3. What are the other names of white box testing?

1. Structural testing
2. Glass boxtesting

4. What are the other names of black box testing?

1. Behavioral testing
2. Opaque testing

5. Conducting detailed black box testing ensures that software is tested thoroughly. Then why there is
a necessity to conduct white box testing?

Industry experience shows that on an average, a well black box tested code have 3 bugs for every 100
lines.

When we are testing applications installed in critical places like flight control, medical devices we cannot
afford to have any bugs since they may cause human life. Hence depending alone on black box testing
may not be sufficient in the applications like above.Hence we conduct white box testing also along with
black box testing in the applications like above

6. Did you have any white box experience?

Sorry, I have not got an opportunity to work on white box testing. This is usually conducted by who have
coding knowledge like developers.

7. What is a test design?

Test design is about identifying and documenting the tests to be used for testing a particular
requirement.

8. What are the different categories of black box test design techniques?

1. Boundary value analysis

2. Equi-valance partitioning
3. Decision table testing
4. State transition testing
5. Error guessing

9. What is boundary value analysis?

Boundary value analysis is a black box test design technique in which test cases are designed based on
boundary values.

If n is boundary, we have to test for n, n-1, n+1.

This means username field takes 6-15 characters 6 and 15 are boundaries.

33
 Manual Testing Very Important Questions and Answers

For boundary 6, we have to test whether the screen allows 5, 6, 7 characters. Screen must allow 6,7
characters since they are valid and must not allow 5 characters.

10. What is Equivalence partitioning?

Equivalence partitioning is a software testing technique that divides the input data into equal partitions
of valid and invalid classes (partitions) .In principle, test cases are designed to cover each partition at
least once.

11. Where do you use decision table testing?

Decision table testing is a good way to deal with business logic where multiple conditions are used to
take decisions.

12. What is state transition testing?

State transition testing is black box test design techniques in which test cases are designed to test the
application trigger from one state to another. To design test cases, identify all the states of the system
and ensure that all states are covered from starting to finish.

13. What are the different categories of white box test design techniques?

1. Statement coverage
2. Decision coverage

14. What is statement coverage?

Statement coverage is the percentage of executable statements that has been exercised by a test suite.

Statement coverage= number of executable statements executed / total number of

Executable statements*100

15. What is decision coverage?

Decision coverage is the % of the decision outcomes that have been exercised by a test suite .The
objective of decision coverage testing is to show all the decisions with in a component have been
executed at least once.

16. out of statement coverage and decision coverage, which one is effective?

Decision coverage is effective because 100 % decision coverage implies 100 % statement coverage, not
vice versa.

17. What is cyclomatic complexity?

Cyclomatic complexity is a white box testing terminology, which is used to give a number of
independent paths in the program. Higher the value of cyclomatic complexity more complex the project

34
 Manual Testing Very Important Questions and Answers

is. Good project are the ones who have less complexity since the maintenance of less complex projects
is easy.

18. What is code coverage?

Code coverage is a white box testing technique. Code coverage describes the degree to which the
source code of a program has been tested. Higher the code coverage is deeper the testing is.

19. What tools do you know for code coverage?

NCover, Jvcover, Rational Pure coverage etc.

20. Is component testing white box or black box?

White box

21. Is regression testing white box or black box?

Black box

22. Is integration testing white box or black box?

Integration testing is a combination of both white box and black box testing. Can also be called as a
grey box testing.

*********** end of chapter 10 –Test design techniques***************************

Chapter 11
Test cases Design
1. What is a test case?
Test case is a set of conditions under which a tester will determine whether an application working
correctly or not.

2. What fields does a test case have?

Following are the fields usually a test case will have

1. Objective
2. Precondition
3. Step name
4. Description
5. Expected result
6. Test data

35
 Manual Testing Very Important Questions and Answers

3. Where do you write test cases?

Depending on the project we can write test cases in an excel file or in quality Centre, test plan tab.

4. How do you know for which modules (or) features you should write test cases?

My lead writes top level requirements in quality center (QC) assign to each team member. We divide
test requirements further into sub-requirements. Then we identify test conditions for each sub-
requirement and create test cases. Test cases are reviewed after that. Reviewed and approved test
cases will go to ready state.

5. What is a test scenario?

Test scenario is nothing but a functional scenario for which testing is to be conducted also called as test
condition.

6.What is the difference between test scenario and test case?

Test scenario is a high level description of business requirements, which is later decomposed into set of
test cases.

A test case is a documented procedure to test a test condition. A Test condition or test scenario can be
defined as an item or transaction which can be verified by one or more test cases.

7. What is a test procedure?

Test procedure refers to the execution of test cases in a particular order. Also known as business process
flow testing or work flow testing.

8. What is the most difficult part of test design?

In my view, identifying the test conditions to be used for testing a given requirement is most difficult
because deep thinking is required to ensure that we cover all business conditions during testing, before
releasing the software.

9. How do you write test cases for a given requirement?

I spend enough time to go through the SRS document and BRSdocument. In case if I am not clear about
any requirements, I discuss the same with my team members and lead. As a team, if we are not clear we
have discussion with business analysts.

After understanding the usecases provided in SRS document completely, I prepare test conditions
ensuring that all normal, additional and exceptional conditions are covered. We call this activity as
testing based on specifications. We also write additional test conditions based on experience, which is
called as experience based testing.

Finally, we prepare test cases that cover both specification based test conditions and experience based
test conditions

10. What is use case and how do you write test cases from a use case?

36
 Manual Testing Very Important Questions and Answers

Use case is a format, which is used to represent the functionality of the application from business
perspective. This is the most commonly used approach for documenting the requirements of the
application. Usecase contains important sections like actors, Normal course, additional course,
exceptional course.

Actors – The users who use the functionality of a particular usecase.

Normal course- general flow of common functionality used by the user

Additional course-Any additional activities performed by the user

Exceptional course- errors that might come while using the usecase

To write test cases for a usecase, we ensure that all conditions mentioned in normal flow, , additional
flow, exceptional flow are covered. Apart from these, we also focus on using test design techniques like
boundary value analysis (BVA), ECP (Equivalent class Partition).

We even apply our experience and write some other tests like NULL validation, Screen refresh etc.

11. Write test cases for ATM?

1. Insertion of ATM card with success

2. Incorrect ATM card of insertion-Leading to unsuccessful operation
3. ATM card of invalid account-Leading to unsuccessful operation
4. successful feeding of ATM Pin number
5. Incorrect ATM pin number feeding 3 times-Leading to unsuccessful operation
6. Selection of language of operation, with success
7. Selection of type of bank a/c with success
8. Incorrect bank a/c type selection in respect to the type of ATM Card inserted leading to
unsuccessful operation
9. Selection of withdrawal option with success
10. Selection of amount to be withdrawn with success
11. Incorrect currency denominations-leading to unsuccessful operation
12. Successful completion of withdrawal of money
13. Amount to be withdrawn in excess of the available balance- leading to unsuccessful
operation
14. Shortage of currency notes in ATM - leading to unsuccessful operation
15. Amount to withdrawn in excess of the daily withdrawal limit- leading to unsuccessful
operation
16. ATM link to the bank server not available at the moment- leading to unsuccessful operation
17. Clicking of cancel button after inserting ATM card- leading to unsuccessful operation
18. Clicking of cancel button after feeding ATM pin number- leading to unsuccessful operation
19. Clicking of cancel button after selection of language of operation- leading to unsuccessful
operation
20. Clicking of cancel button after selection of type of bank a/c- leading to unsuccessful
operation
21. Clicking of cancel button after selection of ATM with drawl- leading to unsuccessful
operation
22. Clicking of cancel button after feeding the amount to be withdrawn- leading to unsuccessful
operation

37
 Manual Testing Very Important Questions and Answers

12. Write test cases for Mobile?

1. Check whether battery is inserted into mobile properly

2. Check switch on/off of the mobile
3. Insert the SIM into the phone and check
4. Add one user with name and phone number in Address book.
5. Check the incoming call
6. Check the outgoing call
7. Check successful operation sending msg and receiving msg
8. Check the correct selection & display of all numbers and special characters.
9. Check the successful deletion of contact name, phone number from address book
10. Check whether network is capturing successfully from service provider
11. If it is GPRS enabled, check for the connectivity

13. Write test cases for Traffic signal?

1. Verify if the traffic lights are having 3 lights (Green, Yellow, Red)
2. Verify that the lights turn on in sequence
3. Verify that the lights turn on in sequence based on time specified (Green light – 1 min,
yellow light- 10 sec, red –light- 1-min)
4. Verify that only one light glows at a time
5. Verify if the speed of the traffic light can be accelerated as time specified based on the
traffic
6. Verify if the traffic lights in some spots are sensor activated

14. Write test cases for an elevator?

1. Check for the maximum weight elevator can carry at a time ( Boundary value analysis)
2. Check whether is capable of moving up and down
3. Check whether elevator waits till close button is pressed
4. Check whether elevator stops at the desired floor for which the button is pressed
5. Check whether elevator indicate if it crosses the threshold limit?
6. Check whether elevator moves up when called from upward and down when called from
downward
7. Check whether elevator automatically stops at each floor?
8. Check whether elevator door opens, if anyone enters in between the door at the time of
closing
9. Check whether elevator operation is smooth
10. Check the display system is giving correct information according to the floor
11. Check the presence & proper functioning of the communication system in case of power
failure.
12. Check the presence & proper functioning of the ventilation system provided
13. Check the presence & proper functioning of the fire fighting system in case of emergency
14. Does the “open door” button work when elevator is moving up or down?
15. Check for the default time of the floor.

15. How many test cases can you write per day? Till today how may did you write?

38
 Manual Testing Very Important Questions and Answers

Number of testcases I can write per day depends on the size of the testcase. On an average, I write
25 testcases per day which comes to 20 pages approximately. I wrote good number of testcases,
approximately above 1000 in my experience of 3 years.

16. Write one test case to demonstrate the standards you follow in documenting the test case?

Test case Login_admin_1

Id
Objective Login as
administrator
into the system
Step id description Test data Expected result Actual Pass/Fail
result
1 Open book http://localhost:8081/bookstore 1.home page
store home should be
page displayed with
title book store
2.page should
have header
with image,
links, home,
register, sign in
and
administration
2 Click sign in Sign in page
from the should be
header displayed
3 Enter login Login: admin 1.should login
name and Pwd: admin into system as
password and admin
click sign in 2.links like
button members,
editorials
categories
should be
displayed
17. What is the next procedure you follow in your organization after writing the test cases?

These testcases will be reviewed and approved by peers. We follow formal review process for
approving testcases written for each functionality.

39
 Manual Testing Very Important Questions and Answers

18. How do you know your testcases are complete?

We know our test cases are complete through

1. Reviews- It ensures that quality of the testcase is good

2. Traceability matrix-It ensures that all the requirements have been covered through
testcases.

19. How do you find whether a testcase is a good testcase or bad testcase?

Good testcase is the one which finds the bug or the one which has probability of finding the bug. A
good testcase should be documented clearly, so that it can be executed by anyone without any
difficulties and confusion.

20. Have you involved in system testing? How do you write system test cases?

Yes. I have involved majorly in functional testing phase of system testing. Functional testing consists
of 2 types. Requirements based functional testing and business based functional testing. For
Requirements based functional testing. We identify test conditions and prepare test cases. For business
process flow based testing we develop test procedures by identifying the business work flows. Test
procedure is a set of testcases executed in a particular order.

I have also involved in some of the nonfunctional testing’s like browser compatibility testing or
installation testing.

21. How do you design test cases for a functionality whose requirements are regularly changing?

Any project without clearly defined requirements will have lots of impact on effort and cost of the
project. I have a very limited control over the change of requirements since it is usually decided by
project manager and client. All I can do is explaining to project manager about the amount of additional
effort I am spending because of requirement change. I would ask him to give me any requirements
which are freezed for initial testcases development. So that I can take up the functionality with changing
requirements little later. This delay might help the client and manager to stabilize the requirements.

22. I want you to design testcases for a new domain which you have not worked before? Do you think
you can handle this?

During my experience, I have worked on projects of various domains. Every time I took up testing on a
new domain I have spent extra effort to understand the domain. To understand the domain, I have
browsed internet for preliminary understanding and also interacted effectively with team members,
business analysts for further information required related to the project. I am confident that I can
definitely design good testcases for new domain also by putting extra effort for thorough understanding
of the domain.

23. Explain one scenario where you were not able to write testcases for a given requirement?

Even though I felt difficulty to understand some of the requirements I have handled, I have never got
into the situation where I was not able to write testcases for any of the requirements. Every time I faced
difficulty I have ensured that I spend extra effort to understand the specific area more clearly through
self exploration and also with the help of the team members.

40
 Manual Testing Very Important Questions and Answers

24. How will you approach to write the testcases?

1. I understand the project by going through testcases

2. Prepare test conditions for normal, additional, exceptional flow
3. Prepare test conditions based on experience
4. Convert them into testcases.

25. Do you update testcases after receiving build based on the application screens?

During execution if we feel any testcase requires an update we will do it with the approval of Lead.
But this work is very limited

26. What is the difference between positive and negative testcases?

Positive testcase:

Positive test case checks whether the system does what it is suppose to do i.e. To check that we
got the desired result with valid set of inputs.

Ex: User should login into the system with valid username and passwords

Negative testcases:

Negative testcase checks whether the system will do what it is not supposed to do i.e. To check the
system generates the correct error or warning messages with invalid set of inputs.

Ex: if user entered the wrong username or password, then user should not login into the system and
appropriate error message should be shown

27. How much % of positive and negative testcases you write?

Approximately 30 % and 70 % negative.

************ end of chapter 11 -Test cases design ************************

Chapter 12
Test Execution
1. What are the Entry& Exit criteria for test execution?

Entry Criteria:

1. Coding should be completed

2. Testcases should be ready& base lined
3. RTM should be updated
4. Test data should be ready& base lined
5. Test environment/setup should be ready
6. Software tools like QTP,QC should be ready and approved

41
 Manual Testing Very Important Questions and Answers

Exit criteria:

1. All test cases must be executed and passed

2. All open bugs/defects must be fixed and closed
3. Test execution summary report must be prepared base lined

2. How do you know have a build ready for testing?

In our project automation build creation happens on every Sunday and build deployment
should be ready by Monday of every week.

However we receive a confirmation mail about successful deployment and URL for testing.

3. How many test cases u can execute /day?

Depends on the size and complexity od testcases. Approximately one executes around 50
testcases per day which comes to 40 pages approximately.

4. How do you run testcases?

Without QC: I will execute the testcases using excel sheet and report actual results and status
(Pass or fail)

Using QC:

All the testcases to be executed will be presented in a testset under "testlab" module of QC.I
will execute testcases from there and report actual results and status (Pass/FAIL)

5. In QC, how do you know testcases which you should execute from the whole list of
testcases?

in "testlab",responsibile tester column contains name of the tester responsible for execution
of each testcase.

6. what will you do if testcase failed?

I will fill the actual result field mentioning the output I have got and I also report the defect
related to failure under defects module of QC.

7. Do you write actual result even for successful test cases?

No.We don't because a testcase is successful only if acual result is same as expected
result.Hence it is implied that if testcase is successful if actual result is same as expected result.

8. Difference between Failed testcases and No run testcases?

A failed testcaseis the one we executed and the result was failed i.e. the actual result was
different from the expected result where as No Run test case is the one

42
 Manual Testing Very Important Questions and Answers

we are not able to execute beacause functionality cannot be reached due to another failed
testcase.

Example:

In a Email application, compose mail link is not opening new mail page. Hence compose mail is
a failed testcase. Because of this we cannot run the testcases that send smail to single, multiple
users with and without attachments.These testacase are called No Run testcases.

9. What is testbed?

Set of hardware, software,and testsetup required for testing a project. Setup installs software
in various systems and how you are going to connect them to perform testing.

10. Have you involved in creating test harness?

Yes. I have an idea of creating test environment comprised of stubs and drivers needed to
execute a test.

11. Have you invlolved in test data creation and test setup?

Yes. I have created test data required for the test case.

12. How do you check whether the password is encrypted or not?

If the password field shows '*' or some other speccial character while entering the password,
it called Password masking but not Password encryption.

Encryption means converting the user entered character/word into a different character/
word before sending over a network. This can be checked with the help of network sniffers.
example software for this is wireshark.These softwares capture every data packet travelling
over the network including ip address of source and
destination computers.by analysing these packets we can identify whether the password string
is encrypted or not.

13. How do you check the broken links?

Many tools are available for this we sue tools like Venn.

14. What are the different tests you have executed?

Requirement based functional tests

Workflow based functional tests

Regression test

Smoke tests

UI test

43
 Manual Testing Very Important Questions and Answers

Browser compatibility tests

15. What is a test log?

It is a report of what tests executed and their status like PASS/FAIL. Also be known as test
execution report. We can genearte this report from QC.

16. Did you observe any application logs during test execution?

Yes. We do observe logs of the application server to check whether server has thrown any
runtime errors.

17. Do you run regression tests for every bug fixed?

no.I don't run regression tests once for every bug fixed.I run regression test once for every
build.

18.Do you run all regresion tests every time?

Depends. If we are sure that fix might not affect other modules we run regression tests
specific to the module of the bugs fixed else we run for enire project.

19. In the modules,you have worked are there any issues identfied after release?

No , significant issues were reported that was affecting functionality.

20. How do you prepare test summary report?

We generally use test execution report from QC to prepare the test summary report.

Test sumary report contains information like which module are stable and which modules
require more focus on testing and overall healthiness of the software.This is an executive
summary for top management about the status of the project.This is done by test manager at
the project level and by test lead at the module level.

21.diiference between code coverage and test coverage?

code coverage checks the % od code coveredduring test execution and test coverage checks
the % of tests executed duringthe execution.

22. What test methodology you are following in your current project?

Waterfall model/ V-model, Agile method(anyone absed on your project)

23. You have only a weektime for release.but you have a work that takes 3 weeks to test. how
will you manage?

1st prioritize teh testcases to execute like MUST EXECUTE, GOOD TO EXECUTE AND EXECUTEIF
TIME PERMITS.I extend my timings to the maximum extent and complete atlest

44
 Manual Testing Very Important Questions and Answers

MUST EXECUTE, GOOD TO EXECUTE testcases.If still some more time is there... as on EXECUTE
IF TIME PERMITS testcases.

24. Have you involved in writing stubs and drivers?

No.I have not got any opportunity in writing stubd and drivers.but i have liitle bit idea on
What stub and driver is.

25.When you fill the data in application form,how do you ensure taht data is stored in the
correct tables and columns?

We can write an SQL query to retrieve data from database and compare the query result with
the data we have filled in the application forms.

********* End of chapter 12 –Test Execution***************************

Chapter 13
Bug tracking
1. Whatis a bug?
Bug is a deviation from expectation
2. Whom do you report when you find a bug? Developer or test lead?
I don’t report to any of them.I report to bug tracking tool.
3. Difference between error, fault, and failure?
Error: A human interaction which produces an incorrect result.can also be called as mistake.
Fault: a manifestation of an error rise software. A fault if encountered may cause a failure.

Failure: deviation of the software from it's expected delivery or service.

4. Whatwill you do if you find a bug?

we report defect in defect repoting tool.while reporting we fill the details like summary,
description, severity, steps to reproduce,status etc.

5. Whathappens after you report the bug?

It will be assigned to a developerby development manager and developer will fix and move the
bug to fixed status.We do retesting to check whether defect was fixed correctly.We also run
regression tests for checking the sode effects.... to fix.

6. Do you run regression tests for every bug fixed?

I run regression tests once for every build.

7. which bug tracking tool do you use?

Bugzilla,QC

8.Whatfileds you have in bug tracking tool?

45
 Manual Testing Very Important Questions and Answers

bugid, summary, description, identified by, asignedto, priority, severity, status, build, H/w
&S/w, reproducible.

9.Whatare the attributes of a bug?

Same as bug.

10.Whatwill you ensure before raising the bug?

I will closely test all the sceanrios related to the are of the bug identified and consolidate the
exact stepsand test data required to reproduce this bug. I also analyze the impact of this bug on
product functionality, to identify correct severity of the bug.

11.why do you need defectId?

To track the bug uniquely.

12.Whatdo you report with bug?

summary

Description

Steps to reproduce

Build number& release version

Severity

Attachments of failure

H/w & s/w

13. Difference between priority and severity?

severity is the functional impact of the bug while priority is business impact

14.Do you fill bug severity? How do you decide?

Yes. I fill severity while reporting the bugs.

Severity:
Critical : bug causes system crash or data loss
Major : bug causes major functionality problems
High : bug causes partial functionality problems
Medium : bug causes data validation issues
Low : bug contains typos,unclear wording or error messages in low visibility
fields.

46
 Manual Testing Very Important Questions and Answers

15.Do you fill bug priority? how do you decide?

Priority is decided by development lead.Guide lines to fill priority is as follows
Priority:
Urgent- Must fix immediately
Very High-Must fix as soon as possible
high -should fix before product release
Medium -fix if time
Low -May be postponed

16.Explain bug life cycle?

---------------
------------

-------------
New:
When a bug is found/revealed for the 1st time, the software tester communicates it to
his/ger team leader(test lead) in order to confirm if that it is a valid bug.After getting
confirmation from the test lead, the software tester reports the bug and status of 'New' is
assigned to the bug.

assigned:
After the bug is reported as NEw,it comes to the development team. the development
lead verifies if the bug is valid.If the bug is valid,Development lead assigns it to a developer to
fix it and a status of assigned" is assigned to it.

open:
Once the developer starts working on the bug, he/she changes the status of the bug to
"open" to indicate that he/she is working on it to find a solution.
fixed:
once the developer makes necessary changes in code and verfies the code , he/she marks
the bug as "fixed".

Retest:

After the bug is fixed the testing team leader assigns it to a tester for retesting it and the
status of "retest" is assigned

Closed:
after the bug is assigned a status as"Retest", it is again tested. If the problem is solved, the
tester closes it and marks

47
 Manual Testing Very Important Questions and Answers

with "closed " status

Reopen:
if the system behaves in wrong way even after bug fix,then tester reopens the bug and
again sends it backto the developer marking its status as "Reopen"
Rejected:
If the developers think that particular behaviour of the system,which tester reports as
bug has to be same and the bug is invalid, in that case, the bug is rejected and marked as
"rejected"

deferred:
sometimes, testing of a partuclar bug stands no importance and can be postponed for
an indefinite period.that time, the bug is marked with deferred status

17. write the sample description for a bug with following behavior.
attachments sent by users with file extension .docx are not able to be opened by receiver.user
is getting file corrupted error.?

Below is sample of how to write bug description.please observe steps to reproduce section:

summary Problem in opening attachments with .docx extension

description
when user sending Email with attachment of format .docx, receiver is not able to open the
attachemnt.system is throwing unknown file format

Steps to reproduce:

Login and click compose mail

fill to,subject, body
click attach button
browse and attach teh files with .docx and .docx extensions
send an email
login with to id
try to open both the attachment and obserrve that files with .doc can be opened where
as files with .docx are throwing format error

Note: PFA screen shot of unkown file format error.

48
 Manual Testing Very Important Questions and Answers

18.advantages of bugtracking tools?

helps in tracking of the bug status from identification to closure
acts as a communication tool between development and testing teams for bugrelated
discussions
it keeps a tral of number of bugs identified,verfied by and rejected by each tester which
helps in performance appraisal of the testers.It also logs the number of bugs fixed by each
developer.
helps in analyzing the stability of each feature(more bugs found for a particular feature
indiactes less stability)

acts as an online database for bug fixes i.e. developer can read the fix procedure of
similar bugs before he fixes a bug.

19.discuss 5 critical bugs you identified?

few examples mentioned below

Ecommerce:
no message was displayed to shop use even when the product was out of stock.
adding the manufactures functionality was not working
Edit link to edit "order status messages" was missing the application.
at the backend, application supported adding sub categories onlny upto 3 levels.
If we select the zone,shipping cart.... list corresponding to zone were not
displayed

CRM:
converting Leads to opportunities was not working.
creating target list for sending campaign details was not functioning correctly
schedule meeetings functionality was not converting the time,based on the time zones
of the user.
creating the cusomer list form visiting crad was not working
applcation allowed creation of campaign even when estimated cost was lessthanthe
budget

20.Whatis the difference between critical bug and major bug?

critical bug means business cannot run without fixing.also called as show stopper.
for example, in a bank application,transferred money is not reaching the destination bank
account,it is critical bug because business cannot run without fixing it.

Majopr bug means it requiresfix as early as possible.but business can be continued.

49
 Manual Testing Very Important Questions and Answers

for example,in a banking application, transaction report is not genearting,it is a major bug
beacuase it needs to be fixed as soon as possible.however businesscan be continued with it.

21.discuss couple of hot technical discussions you had with developer?

ecomerce:
in pour project, to add product to cart customer must click on the product and
go to the product page and add to the cart.I proposed that "ADD TO CART" button should be
present next to each product.
so that customer can directly add the desired product to cart without the necessity to naviagte
to a new page.development did not agree with this beacause it invloved considerable design
change,but our manager was very much impressed with this suggestion and pushed it further
to business analysts team

finally it got the approval and change was implemented

CRM:
In our product we have to collect primary and alternative phone numbers from
customer.developer made both of them as mandatory.I have stated an opinion that primary
phone no. can be manadatory and alternate phone can be optional.developer opinion was that
customer information is so critical and it is good if we make both as mandatory.more over he
also felt if we give only one phone no as mandatory,users of application might neglect
capturing the other phone no..

I am not convinced with this bcoz all customers might not mainatain 2 phone nos. and they may
not be interested to share other close relatives no as an alternative.this might also force users
of the application to enter a dummy no and DB might end up with wrong entries there ther bu
wasting lot of time during followups.
I have also mentioned let us motivate the customer to give an alternate phone no rather than
compelling for the same.

after discussion between testlead,DevLead,.Test Manager and DEV manager they have
agreed to make alternattive no as optional
22.Whatis Retesting?
Re-testing means verifying the bug has been fixed correctly

23.diff between regression and retesting?

Retesting is conducted to ensure that bug has been fixed correctly by developer. and
Regression testing is conducted to ensure that there are are no side effects due to bug fixes ot
it should not have impact on already existing functionalities

24.Whatis the process u follow for conducting retesting?

50
 Manual Testing Very Important Questions and Answers

1.first I understand the bug description and steps to to repoduce the bug from bug
tracking tool.optionally I also try to understand the root cause given by Developer for this bug
2.I identify test scenario or conditions to be used for verifying this bug
3.I will run the test case which found this bug and ensure that this bug is not appearing.

4. I also run the test cases which cover all the test conditions identified for verifying this
bug.incase if some test conditions are not part of any test acse I update test case document
with these additional conditions
5.after completion of testcase execution document I document test tests executed to verify
this defect in comments section of bug tracking tool with my time stamp.

6.I will send the tests I executed to retest the bug for peer review (LEad or colleague) and based
on the approval I update the status of the bug to closed".

25.Whatis the purpose of comments section?

comments section is used to
-document the comments provided by developer during bug fix
-document the tests used during retesting
-document the retest review and approval
-document the tester comments in case of defect reopen
26.how do u handle aggressive developer?
it does not matter to methe developer is aggressive or not,as long as I ensuremu
communication is professional.I always ensure that I communicate all the issues in clearly
documented from through email or through nug tracking tool.incase of difference in opinion I
try to add business cases,which demands the fixing of the bug raised by me.though I provide all
necessary information,if developer is not taking it professionally,I try to work with that bug
though my lead. how everI ensur max not to involve my lead since he has to spend his valuable
time to work on this issue.
27.u are reopening lots of bugs fixed by a specific developer.Whatwill u do in this situation?
metric on report is usually collected by dev manager and he interacts appropraitely with
developer.from my side I might bring to test lead / test manager's notice just to make them
aware that I am not able to complete verification of lots of bugs since many reopens are
coming.I fthey feel it is necessary they will discuss with development manager appropriately
28.there is a bug is appearing at customer place that is not reproducible
inyoursystem.Whatwill u do?

1. I will confirm with customer whether steps to reproduce are correct

2. I will compare whether environment of customer system and my system is same in
terms of OS version, Service packs, Patches installed, Browser Type and browser version
etc..
3. I will ask the Customer to send application logs and analyze them to understand the
activities performed by Customer leading to this scenario.
4. Still if it is not reproducible,I will also take the list of additional software running in
Customer System and check whether any of them might cause an issue to our appl.

51
 Manual Testing Very Important Questions and Answers

29. how will u handle the developer who is not agreeing to the bug u reported?
I will explain the business scenarios in which this bug will be affecting customer and the impact
of this bug to the cust. I am sure he will understand and explain the bug from the business point
of view and still he is not and I discuss with my lead and he will take it forward accordingly
30.Whatis showstopper?
Show stoppper is a critical bug identified before software release due to which software
release must be postponed. Since we are stopping the show of releasing the software this is
called as Showstopper.
************ End of chapter 13 - Bug Tracking *************************

Chapter 14

Test closure

1.What is an entry criterion for test closure?

Decision to stop testing

2. who takes this decision?

test manager

3.what parameters test manager considers to take decision to stop testing?

important parameters test managers looksis

1. whether all requirements have been developed or not

2.whether all requirements have been covered through testing

3.whether all defects have been handled through fixed or deferred status

4. what is exit criteria for test closure?

1.checking whether planned deliverables have been delivered

2.finalizing the archiving testware

3.handover of testware for the maintenance

4.analysing lessons learned for improvement of test maturity

52
 Manual Testing Very Important Questions and Answers

5.What is testware?

test ware is artifacts produced during the testing process. test ware

includes testcases, test plan, automation scripts, test data, test

environment setup and clear up procedures and any in testing

6. What is lessons learnt document?

Lessons learnt doc is a document that captures the good and bad lessons

Learnt during project execution.it contains following sections

1. Top 3 significant factors for proj success

2. Other notable factors for proj succeses

3. Proj short comings and solutions

******************* Chapter 14 -Test closure **********************************

Chapter 15
Software Metrics

1. What is s/w metrics?

S/w metric is a measurement of how well an organisation is performing with respect to
different activities it carries out
2. Why s/w metrics are essential?
S/w metrics are very important bcoz they help u to understand
1. Where organisation is doing well?
2. Where improvement is required?
3. How is the trend analysis with respect quality and productivity?

in sum, if u don't measure any work u can't control and improve

3. What metrics u follow inyourorganisation?

53
 Manual Testing Very Important Questions and Answers

Some of the metrics we follow are

1. Defect removal Efficiency (DRE)
2. Productivity
-test case preparation rate
- test case execution rate
3. Defect density
4. Test effort
5. Defects found
6. Test back logs
7. Test coverage
4. What is DRE and how it is useful?
Indicates the efficiency of defect removal methods, as well as indirect measurement

Of the quality of the product.higher the ratio better the quality of the product and

Efficiency of testing team.

DRE=No of defects found during testing/( no of defects found during testing+ No of

Defects found at customer place)*100

5. What is productivity and how it is useful?

Measure the performance of an individual at work.this helps manager to analyse what extent
each team member is developing the o/p.

Test case preparation rate= no of test cases designed/No of hours spent

Test case execution rate=no of TC's executed/no of TC's planned to execute

6. What is defect density and how it is useful?

no of defects found per 1000 lines of code. this metric indicates the quality of the

Product under test.

defect density= no of defects found/ total no of lines of code(thousands)*100

if 2 modules A and B are present and module A has 20 bugs and module B has 10 bugs

we can't say module B has better stability compared to module A.

This is bcoz it also depends on the lines of code

54
 Manual Testing Very Important Questions and Answers

let us say module A has 200,000 lines of code and module B has 10,000 lines of code.

Defect density of A=(20/200)*100=10 - more stable

Defect density of B=(10/10)*100

this means defect density of module is A less than module B hence module A has more

stability than module B

7.What is test effort and how it is useful?

test effort is the amount of work spent in hours or days or weeks in testing, in

relation to the effort spent to in the development activities. this metric will give

us an indication of the level of investment in

testing

test effort= amt effort spent on testing ( in hours or days)/total effort spent on

proj(in hours or days))*100

test effort should be around 35% of proj effort

8. what is test backlog and how it is useful?

the no of resolved defects that are yet to be retested by testing team. indicates

how well test engineers are coping with the development effort
s

9.what is test coverage and how it is useful?

helpful to find the extent to which testing cover the product's complete

functionality. this metric is an indication of the completeness of testing.

test coverage= (no of TC's ececuted/Total No of TC's)*100

at the end of each test cycle test covearge report will be prepared.

10.Defect detection rate(DDR)?

this is the effort required to find defect.this show how fast the defects are being

55
 Manual Testing Very Important Questions and Answers

found.this is also known as time to find a defect or defect finding rate.

DDR=total no of valid defects found/total execution effort

11.DRR(defect rejection ratio)?

it identfies the % of defects that were rejected out of total no of reported defects.

higher the value indicates that testing team did not understand the project well.
DRR= (no of defects rejected/ total no of reported defects)*100

12.deviation?
it represnts the % deviation in the actual effort.
effort deviation=((estimated effort-actual effort)/estimated effort)*100

13.what is the different between project metrics,process metrics, product metrics?

product metrics describes the characterstics of products such as size ,complexity,

design features, performance and quality level .

ex's:
1.time to find a defect
2.time to solve a defect
3.test covearge
4.defect density
Proj metrics describe the proj teams ability to perform the proj execution.
ex's:
1.test effort
2.productivity

process metrics can be used to improve the efficient of an existing process used in

s/w development and maintenance.

1.bad fix ratio
2.defect removal efficiency
3.development backlog
4.testing backlog
**********end of 15.test metrics*******************

Chapter 16

Change Management Process

56
 Manual Testing Very Important Questions and Answers

1. What is a change?

Change is is nothing but any modification to the existing document or

application.Change could be of addition,deletion or modification.

2. Who can request for change?

Change request can come from external or internal.This means either
customer can ask for change or internal team member also suggest for a
change.
3. How do u manage changes inyourproject?
We follow change management process to handle change the requests.
4. During requirements gathering the phase I have some requirement to be
included in the project? Should I follow Change management process?
No. during requirements phase what ever the requirement u rlooking for
can’t be called as change. This is bcoz project is still in requirement process
and ur additional requirement can’t be called as change.
5. At which phase of SDLC change management process?
Change management process starts immediately after requirements are
baselined.
6. What is Impact analysis?
It refers to analysing the impact of changes made to the project.This term
usually represents the impact to SRS, Design and test cases bcoz of code
change.
7. Did u suggest any changes?
In the e-commerce project I worked, there is no provision for adding a
review for the product. I have suggested for that change and it has been
accepted.
8. Can u explain change mangement process u follow?

57
 Manual Testing Very Important Questions and Answers

9. What is CCB?
CCB means Change Control Board.CCB decides whether the change
requested is accepted or not.This decision is taken after initial analysis of
change requested by the user.
10.Who are present in CCB Team?
Managers,Architects and business analysts

………..

Chapter 17

Release Process

1. What is the entry criteria for release?

Entry criterial for release are
1. System testing results must show that all requirements are
completed and project is stable.
2. Alpha and beta testing must be completed
3. All medium and above security bugs must be fixed.
4. Release package is available
5. Release CD label is ready
2. What is the release process u follow? What is invlovement in release
process?

In our organisation,release process is coordinated by a person called

Release Manager.after succesful …testing release manager sends email for
all stake holders,development manger,test manger,documentation manger
for their concurrence (approval) for final release.test manger forwards the

58
 Manual Testing Very Important Questions and Answers

same mail to team members requesting internal approval.based on internal

approval test manger can send approval to release manager.
As a testing team member, I go through defect tracking tools tool
and check whether all defects are fixed.in case any defects are not
fixed ,communicate the same to my test lead and test manger, sharing my
opinion regarding each bug whether it must be fixed before release or it
can be fixed later to release. Test manger takes final decision whether to fix
or not after the discussion with development manger.
I further involve in preparing release notes,where I document known
issues in my module along with issues resolved from previous release.

3. What is release note? What is ur contribution to release notes?

It is document attached with the s/w we are releasing. It is also known as
READ ME file. I have contributed to update 3 sections of this doc which
were related to my module. They are
1. New functionaties in current release
2. Issues resolved from previous release
3. Known issues of current release

4. Should we fix all the bugs before release?

Not required. If sufficient time is avaialable we will fix all the bugs before
release,else some low priority bugs can be postponed for next release. Some
times if a medium or high priority bug does not have a solution at present that
issue can b documented in release notes and proj can be released.
5. what if you don’t have a solution for one of the critical? Do u stop release?
It depends on what makes the bug critical. For example, if my application is
not running on firefox browser which is one of the basic requirement of the
product, I will not stop release instead I add this in release notes under the list of
known issues. I give a work around to customers to use IE instead of firefox. Other
wise if the issue is transferred money is not reaching to friend in banking
application I prefer to postpone the release.
6.how do u know that u are completely ready for project release?
We have a release check list doc to check item by item to be complted by
all the teams before release. Release check list looks like below

59
 Manual Testing Very Important Questions and Answers

Items to be considered Owner Y/N

Work products related development
Are all the work products
reviewed as per review
guide lines?
Are work products
planned for release
updated with appropriate
version numbers and
base lined in the CM
system
Does all requirements are
developed as per SRS?

Testing related Test team

Havge the work products
been tested as per test
plan
Have the known issues
limitations been
discussed?

Have the test reports

been genearted?
SQA related SQA
Have the work products
gone through planned
V&V procedures for the
release?
Release Release
Have release notes been
prepared with necessary
information and
reviewed?
Has the release
notification been sent?

60
 Manual Testing Very Important Questions and Answers

Suggestion II:
To reduce turn around time for training for new hires,I have suggested an
intranet website which conatina lots of recorded videosfor understanding
common functionalities of the product. Over period of time it has incorporated
more than 50 videosand helped for new hires as a self servicetraining portal.

7. What is root cause analysis(RCA)?

RCA is a systematic approachto get to true root causes of any problem identified
in the proj. the primary aim of RCA is to identify the root cause of problem
inorder to create effective corrective action that will prevent the problem from
ever re-occuring.
8. What are techniques of RCA?
Many techniques are available. Following are familiar
1. Causal factor tree analysis
2. Fishbone analysis

9. Who will be involved in RCA?

All the stake holders related to the work will be partitioned in RCA. For ex: if many
defects are Re-opened in particular module, developers in corresponding
module, architect, test engineer,development and test leads and managers will
participate in RCA.
10. What is the difference between QC and QC?
Quality assurance is known as QA, is team responsible to define the
processes,templates, guide lines and check lists to develop the s/w.
Quality control: also known as QC, is the team responsible for checking the poroj
quality through various activities like executing tests, reviewing doc’s, verifying
check lists. QC is nothing but testing team.

QA QC
61
 Manual Testing Very Important Questions and Answers

Works at organisation level Works at proj level

Prvides new techniques to prevent Identifies the defects in proj
defects
Reacts based on the f/b from QC Finds and logs defects for QA analysis
Identify tools required at organisation Use the tools provided by QA
level
Does regular quality audits to verify the Conduct various testing activities to
adherence to process by each project check quality of s/w before it is
released to client

11. what is the difference between verification and validation?

Verification is the activity of chking whether the proj developer by
following defined process.( are we building the prod right?)
Ex: reviews, check lists, audits
Validation:
Is the activity of chking whether the proj developed is working as per
requirements.(Are we building the right prod?). also called testing.
Verification invloves reviews and meetings to evaluate odcs, plans, code,
requirements and specifications to confirm whether items, processes, services or
doc’s confirm to specified req’s or not. This can be done with help of check lists,
issues lists, walkthroughs and inspection meetings. The purpose of verification is
to determine whether the prod’s of a given phase of s/w development cycle fulfil
the req’s established during the previous phase or not.
Where as validation is the determination of the correctness of final program or
s/w product produced from a development proj with respect to the user needs
and req’s. this invloves actual testing of the product and takes place after
verifications are completed.
12. What verification techniques u follow?
1. check list
2. reviews
3.audits

62
 Manual Testing Very Important Questions and Answers

13. What is SEPG?

s/w engineering process group or the SEPG group is a group of process
specialists. These individuals facilitate the definition, maintianenance, and
improvement of s/w processes used by the organisation.
14. difference between QA and SEPG?
Both are the same. Terminology differs depending on organisation.
15. what is quality audit?
Quality audit is the process of systematic examination of quality system
carried out byinternal or external quality auditor or an audit team. Quality audit is
an imp part of organisation’s quality managemnet system.
16. What is risk?
Risk is an event of failure that has a probability to occur during proj execution.
17.what is the difference between problem and risk?
Problem is sthng which team is suffering now and risk is some problem which
may occur in future.
18. discuss few risks s/w projects have?
Some of ex risks in the proj are:
1. Team turn over(team members leaving the proj)
2. Domain of the proj was new
3. Unexpected long time leave of the employees
4. Knowledge of technology
5. Knowledge of products and req’s developing during
course of the proj
6. Complexity of the proj
7. Visibility of proj

19. what is contigency plan?

It is solution to be adopted if risk arises.

63
 Manual Testing Very Important Questions and Answers

20.what are the difference categories of risks?

Technology risks:
Technology risk generally leads to failure of functionality and
performance of the prod.
Some ex’s of Technology risks are:
1. Continous changing requirements
2. Outdated hardware or insuffficient hardware exists for runnning new
s/w products
3. Early adoption of new technology
Resource risks:
Human resource risks can involve staff changes, a lack of skilled resources.
Some ex’s of resource risks are
1. Team turnover near to release may affect detailed tetsing of proj.
2. Failure to resolve the responsibilities may overlap responsibilities
3. No proper communication b/e team members.
Schedule Risks:
Schedule risks impact the project schedule and may lead to proj failure if
they are not addressed properly. Some ex’s of schedule risks are
1. Failure to identify the complex functionalities & time required to
develop those functionalities
2. Unexpected project scope expansions
External risks:
Risks beyond the direct control of the proj team caused by external
environmental factors or industry factors.
Some ex’s of External risks are:
1. Potential regulatory changes
2. Potentail economic changes
3. Potential company changes
21. How risks are handled?
64
 Manual Testing Very Important Questions and Answers

Risks are handled through risk management plan which has following 4
stages:
1. Risk identification:
In this stage, risk identified and the name is given to the risks
2. Risks quantification:
in this stage , risk impact and probability is quantified as low ,
medium, high, and critical
3. Risk reponse:
In this stage, how risk can be mitigated will be planned
4. Risk monitoring and control:
In this stage, continual risk is monitored and handled incase if
it appears.
22. What are baseline documents?
Baseline documents are the doc’s, which have been approved by the stake
holders and will not have any ore changes. Baseline doc’s have undergone
“review” process. Once a doc is baselined it can’t changed unless there is a
change request duly approved by stake holders.
23. What is six sigma?
Six sigma is a methodology focussed in creating break through
improvements by managing variation and reducing defects in processes across
the enterprise. It is a methodology aimed to reduce defect levels below 3.5
defects per one million opportunities.
24. What is the difference between CMM and CMMI?
The CMM means capabilty maturiy model, used to judge the maturity of
the s/w processes of an organisation and to identify the key practises that are
required to increase the maturity of these processes. The CMM is organised into
five maturity levels consisting of initial, repeatable,defined, managed, and
optimising.
CMMI means Capability maturity model integrated. CMMI is an integration
of all divisions in IT industry like procurement, HR, Travel and s/w.
25. What is the difference between project and product?
In project
65
 Manual Testing Very Important Questions and Answers

1. Specifications will be given by client

2. Client views/ requirements will be developed
3. Once developed proj is completed
4. Customization usually limited since developed for specific client
requirement.
In product:
1. Company deisgn product
2. Company with own views based on market develops the prod
3. Never ending process
4. Customization is possible.
26. what is difference between proj and prod testing?
Product is never ending hence very goodfocus should be given for
regression testing keeping long term view of maintenance. Usually products are
developed keeping many clients across globe. Special emphasis should be given in
products for customization and internationalisation.
27. How do u introduce a new s/w QA process?
It depends on the size of the organisation and the risks involved. For large
organisations with high-risk projects, a serious management buy- in is required
and a formalised QA process is necessary. For medium size organisations with
lower risk projects, management and organisational buy-in and a slower, step by
step process is required. For smaller groups or projects, an adhoc process is more
appropriate.
28. what is phase containment and defect prevention?
Phase containment is incorporating QA into all the phases of SDLC. IT
results in defect prevention. If QA team performs requirement review, design
review, code review, defects would be few when actual apppl is tested. That
means we have prevented many defects by performing reviews at each stage of
SDLC.
*********** -End of Chapter 17 -Release Process - ***************

Chapter 19

66
 Manual Testing Very Important Questions and Answers

Web Application Testing

1. How web testing differs from client server testing?
Both require thorough functional testing. Since web appl’s are exposed to entire world
through internet they need more emphasis on security testing, performance testing and
browser compatibility testing.
Below are the detailed differences

Client server Web-based

1. testing is performed on .exe installed on 1.testing is performed on content streamed
local computer from webserver using browser
2. the no of clients are unkown 2.no of clients is difficult to predict
3. Low multimedia type of data 3. rich multi media type of data transaction
transaction
4.clients and servers are the entities to be 4.client,server and network are the entities
tested to be tested
5.designed and implemented on intranet 5.designed and implemented on internet
environment environment

2. what are the difference types of testing required for web appl?
1. Functioanlity testing
2. Usability testing
3. Interface testing
4. Compatibility testing
5. Performance testing
6. Security testing
3. What will be tested during functionality tetsing?
1. Whether all external links and internal links are going to correct pages
2. Whether all screens or forms functionaning corrrectly
3. Check whether site can be crawled by difference search engines.
4. Check if all DB queries are executing correctly, data is retrieved correctly and
also updated correctly.

4. What will be tested during usability testing?

1. Are all dropdowns on the screen sorted correctly?Alphabetic sorting is the default
unless otherwise specified

2. Have the menu option which apply to ur screen got fast keys associated?

3. Does the tab order specified on the screen go in sequence from top left to bottom
right> this is the default unless otherwise specified.

4. are all read only fields avoided in the tab sequence order?

5. are all disabled fields avoided in the tab sequence?

67
 Manual Testing Very Important Questions and Answers

6. can the cursor be placed in micro help textbox by clicking on the textbox with the
mouse?

7.is the cursor positioned in the 1st i/p field or control when the screen is opened?

8. is there a default button specified on the screen?

9. when the user Alt+ tab is to another application does this have any impact on the
screen upon return to the appl.

10. incase of limitation in no. of characters do all edit boxes indicate the no. of
characters they will hold?

5. How to conduct interface testing?

The main interface in any web application server interface.

1.webserver and application server interface

2. application server and DB server interface

Below are the tests to conduct for interface testing?

1. Check error msgs between these servers are handled properly and appropriate
error msgs are displayed to the end user.
2. Check what happens if connection to webserver or application server is reset in
between?
3. Chk what happens if user interrupts any transactions in b/w?

6. what do u test in compatibility testing?

1.browser compatibility testing?

2. operating System compatibility

3. hardware compatibility

7. how to conduct browser compatibility testing?

Below is the procedure u can follow for browser compatibility testing

1. Identify all of the operating System and browsers u wish to test

2. Create a compatibility matrix that defines which browsers will be tested on each OS.
3. Run regression tests on all browsers/OS combinations
4. Run a portion of ur functional test on each browser during functional testing.

Below r the imp areas to focus during browser compatibility testing.

1. CSS validation
2. HTML and xhtml validator

68
 Manual Testing Very Important Questions and Answers

3. Alignmentof all images

4. Page validations with and without javascript enabled
5. Impact of change in font sizes.
6. Page zoom out and zoom in
7. Page layout in dif solutions
8. Page content alignment
9. Ajax functionality

8. There are 500 test cases and u have to test them on all kinds of
browsers(IE,mozilla,netscape..etc). if there is a land time, what is the best approach to follow?

1. categorize all test cases like user interface,functional.

2. usually most of the functional testcases works on all browsers.

3.so first execute usability testcases, if the time is there then go for remaining cases.

9. how do u conduct browser compatibility testing?

There are many tools for doing this. These tools will provide multiple browser environments.
Some of them are

1. Adobe browser lab

2. Browser shots
3. Super preview
4. Litmus
5. Spoon browser sandbox

10.why perfromace testing is essential for web appl?

Since most of the websites are internet based, your website may be popularised over a
single day and millions of users will be accessing your appl. Ur application must support such a
heavy load. Hence performance testing is very essential.

11.why security testing is essential for web appl’s?

Since web appl’s are accessed from any where they are easy targets to hackers. If web appl’s
are hacked,following are the issues

1. Loss od Customer confidence

2. Harm to ur brand
3. Disturbance your online means or revenue collection
4. Website down time, time loss and expenditures in repairing damage
done(reinstalling services,restoring from backups)
5. Cost associated with securingweb appl’s against futire attacks.
6. Related legal fees and implications for having such lax security measures in place.

12. What should we test in security testing?

69
 Manual Testing Very Important Questions and Answers

Below is the brief of various security tetsings, we conduct on the project.

1. URL manipulation: manipulating the URL with difference data

2. Directory access: accessing the directory for its entire data
3. SQL injection:unauthorised access to DB.
4. Cross site scripting: runnning the scripts on the web server and stealing the
inofrmation.
5. Cookies: manipulating cookies for gaining unauthorised access

13. what are the typical problems in web testing?

The following are some of the typical problems discovered through web testing?

1. broken links

2. pages don’t render properly with some operating sys’s and or browsers.

3. it takes too long time for some pages to render

4. web page design(fonts color scheme layout) does not meet requirements.

5.feeds don’t work properly

6. pages are not accessible for visually impaired.

7. some of the cntrls are who are supposed to be hidden might not be hidden in all the
browsers.

8.cookies don’t work properly

9.concurrency issue (session problems) when multiple users are on the same page.

10.users have inappropriate access to roles or content.

11.pages on website are not properly validated and don’t confirm to industry
standards(CSS,HTML,XHTML)

12.web client can’t handle some of the msgs returned by server.

13.data obtained through web pages are not captured and or stored properly in DB.

14.server log does not properly track transactions.

14. what is cookie?

Cookie is small infor stored in text file on user’s hardrive by webserver.this is infor is
later used by web browser to retreieve infor from that machine. Generally cookie conatains
personalised user data or infor that is used to communicate between difference web pages.

Cookies are of 2 types:

70
 Manual Testing Very Important Questions and Answers

1. Session cookie:

This cookie is active till the browser is open. When the browser is closed, this session
cookie gets deleted.

2. Persistent cookie:

The cookies that are written permanently on user machine and last until the expiry date.

15. how to test cookie?

1. check cookie expiry:

1.if the appl’s using persistent cookie type, then cookiemust expire as soon as
expiry date and time reached.

2. if the application using session cookie types, close the appl’s browser. Cookie
should expire

2. by disabling cookies check that application is showing appropriate error msgs like
“enable cookies in ur browser for using complete functionality of this site”

3. check whether sensitive info in cookie is encrypted or not

4. check whether application crashes or data corrupt by selectively rejecting soe

cookies.

5.make sure that there is no overuse of cookies. Overuse of cookies will annoy users if
browser is prompting for cookies often.

6.check cookies are correctly working in multiple browsers.

16. how do u test a web online application in off line mode?

Simple. Confifure in intraner webserver and access it. there is no need to have internet
for accessing the web appl.

17. what errors can occur when the page loads?

1. page can’t be found or server error.

2.images/activex control not loaded.

3.alignement problem in the page.

4.page freeze

5. control not working

71
 Manual Testing Very Important Questions and Answers

18.how do u test broken links?

There are so many broken link checking tool available.these tools will send client HTTP
requests to web server and analyse the response code to check whether link is active or
broken.. some of them are broken linkschecking tools are..

1. xenu’s link sleuth.

2. Dead links
3. W3C link checker
4. Link cheker pro.

19.how do u conduct CSS,HTML,RSS FEED validation?

There are many tools avaialable for CSS. HTML and RSS feed validation. Some example
tools are 1. CSS validator.

2. HTML validator.

3.RSS validator

4.Validator.w3.org

5.feed validator.org

6.valoidome.org

20.what is configuration testing in web testing?

This is a process of tetsing the application against difference environments, difference

hardwares and difference softwares.

21. what is transaction tetsing in web testing?

Transaction testing verifies the ability of the application to assure the integrity and
effectiveness of the business transactions and their data conetent with respect to internal
application systems.

22.diff between thin client and thick client? Web based projects are thin or thick client?

For ex: a registration page filled by the customer must be validated for correct mail format,
valid characters in username etc. this validation can be done at client side or the form data
can be posted to server and validation can be done at server side. If validation is done at server
side. If validation is done at client side, code of the client s/w is large (thick). If validation is
done at server side, code of the client s/w is small (thin)

Thick client is the one where validation happens at client side and thin client is the one where
validation happens at server side.

72
 Manual Testing Very Important Questions and Answers

Usually web appl’s are thick clients bcoz validation haapens at client side using java script and
windows based appl’s are thin clients.

23. what is the difference between webserver and application server?

Diff between appserver and a web server.

1. Web server serves static html pages or gif ,jpegs etc. an application server is used
to run business logic or dynamically genearted presentation code. It can either
be .NET based or J2EE based.
2. A web server understands and supports only http protocol whereas application
server supports http,TCP,IP and many more protocols.
3. Webserver clients can include http,html , where as application server clients include
GUI’s and webservers
4. Webserver delegation model is fairly simple,When the request comes into
webserver. It simply passes the request to the program best able to handle it.(server
side program). It may not support transactions and DB connection pooling.
5. Appl server is more capable of dynamic behavior than web server. We can also
configure apppl server to work as web server. Siply application server is a super set
of webserver.
6. Web servers are used for small to medium sized appl’s . these are less reliable and
secure compared to application serverslo which are used for enterprise appl’s.

24.list out few application servers and web servers?

Web servers:

1. Tomcat
2. Apache
3. Personal web server
4. Imatix

Appl server:

1. IIS
2. Weblogic
3. Websphere
4. Jboss

25. list out various technologies used in multi tier web based appl’s and discuss their
advantages?

List out various technogie used in multi tier web based appl’s.

Technologies layer purpose

1. Javscript,html,flash,flex,ajax,silver light Front end For gui design and
validation

73
 Manual Testing Very Important Questions and Answers

2.IIS,weblogic,websphere,jboss,apache,tomcat Middle These are application

and web servers for
hosting/deploying the
appl’s
3.ASP.NET,PHP,JSP Middle For business logic
implementation
4.JDBC,hibernate,ADO.NET Middle DB connectivity
5.oracle ,SQL server,MYSQL,Post GRE SQL,DB2 Backend Databases for
datastorage
6.XML All layers Fot temporary Data
storage,data
communication
between front end to
middle layer, middle
layer to back end
26. what is distributing architecture?

It is a concept of using multiple application and DB servers at difference locations across the
world to reduce n/w traffic there by increasing the application reponse time. For ex:sites like
yahoo,google can have following distributing architecture.
DB server(USA) Appl server(USA)
User1

(USA)

DB
Server(India)

User2(india)
Appl
server(India)

User3
(india) Appl
server(UK)

User N

27.how do use in XML in projects?

74
 Manual Testing Very Important Questions and Answers

Xml is used in many aspects of web development as follows.

Data sharing:

In the real world, compute systems and databases contain data in incompatible formats.

Xml data is stored in plain text format,which provides a software and hardware independent.
Way of storing data. This makes it much easier to create data that difference appl’s can share.

Data Separation:

If u need to display dynamic data in ur html doc,it will take a lot of work to edit the
html each time the data changes. With xml, data can be stored in separate xml files. This way u
can concentrate on using html for layout and display and be sure that changes in the
underlying data won’t require any changes for the html. With a few lines of java script, u can
read an external xml file and update the data content of ur HTML.

Data Transport:

With xml ,data can easily be exchanged between incompatible systems. One of the
most time consuming challenges for developers is to exchange the data between incompatible
systems over the internet. Exchanging data as xml greatly reduces this complexity,since data
can be read by difference incompatible appl’s.

Enhanced data availability:

Since XML is independent of hardware,s/w and appl, xml can make ur data more useful
and easily avaialbe. With xml , ur datacan be available to all kinds of “reading
machines”(handheld computers, voice machines, news feeds. Etc),which make it mw inore
available for blind people, so people with other disabilities.

Creating new internet languages:

A lot of internet languages are created with xml.

1. XHTML the latest version of HTML

2. WSDL for describing available webservices
3. WAP and WML as markup languages for handheld devices.
4. RSS language for new feeds.
5. RDF an OWL for describing resources and ontology
6. SMIL for describing multi media for the web.

28. what is webservice testing?

A web service is a s/w component that is described via WSDL and is capable of being
accessed via std n/w protocols such as but not limited to SOAP over HTTP.

29. what is webservice testing? how is it done?

75
 Manual Testing Very Important Questions and Answers

Webservice testing is nothing but testing whether the web service component returns
correc t data to various web service requests. This can be done with the help of tools like SOAP
UI,Stylus Studio web service call composer,WSDigger.

30. what is browser usage %?

Statistics of Dec 2010:

Browser version Market share % DEC 10

IE 8.0 29.55
Firefox 3.6 25.29
Chrome 8.0 11.67
Ie 7.0 11.32
IE 6.0 5.79
Safari 5.0 3.49
Firrfox 3.5 2.94
Chrome 10 2.1
Firefox 3.0 1.67
Opera 10.6 1.19

**********************END ***********************************

20.Additional testing questions

1. How do u work if u want to test a project which is entirely new domain?

I am sure I can easily mould myself to work in new domain as I am a flexible and a quick learner.
The approach I would follow is:

a. Understand the business outline of my customer

b. Go through various sites in internet and understand the domain fundamentals
c. Study the customer application SRS and the relevant documentation by simultaneously
Matching domain skills with business needs od my customer.

This way I can understand 90-95% of the project.May be I would like take help of colleagues and
Lead for remaining 5-10% for understanding the project.

2. How do u test a project if no documentation is available for it?

I believe every product will have user manual and admin manual even if the SRS is not available.
These manual are one of the best place for me to understand the product. Worst cases if u don’t
even have these manuals, I believe context based help is provided for the functionality of each
screen. Using the domain knowledge I have I will explore each screen to understand the

76
 Manual Testing Very Important Questions and Answers

workflow of the application. We call this activity of exploring the application for understanding
it’s behavior as exploratory testing.

3. Which SDLC models u used in ur project? Justify why used?

I have majorly involved in 2 sdlc models i.e V-model and agile . our company was using v-model
extensively since in this model testing goes hand in hand along with the development and hence
helps in effective time utilization. Now a day’s most of the projects have started using agile
model for projects in which the requirements are not fixed initially.
4. discuss various difficulties u have faced as a test engineer?
Common difficulties that test engineers face are:
1. not up to date SRS:
changes made to the requirements may not be updated in SRS some times. So there will be
a minor difference between application developed and SRS. And since test cases are
written and executed according to SRS ,certain bugs reported become invalid.tester get to
know about the changes in the req after reporting the bug during the discussion with dev
team.
2. Convincing the developer with respect to reported bugs and rejected bugs:
Another challenge which I faced was to convince the developers regarding the bugs. I was
susccesful most of times in convincing the developers bcoz I always explained the
importance of fixing the bug from business perceptive and customer’s point of view.
3. Delay in the relaease of build:
Some times build releases may be delayed. Due to which detailed test coverage gets
affected as less time is available
4. In availability of discussion time :
Some of the bugs require discussion before the rejection so we need to buy some of dev’s
time. Due to time zone differences and busy schedules of developer’s at times,discussions
were prolonged for more than 2 weeks where they ahd to be completed within 2 days as
per SLAs.
5. What is agile testing?
Agile testing is a testing practice for a project using agile methodologies such as extreme
programming(XP). Treating development as customer of testing and emphasizing on test
first design paradigm.
6. Technical or domain skills which one is most important for test eng?
In my opinion , both r imp.technical skills helps in interacting with developer most
effectively in his lang and domain skills helps to understand and test the product effectively
from end user point of view. Any how, in the order of preference of domain skills are more
imp than technical skills for test engineer.
7. I have testing work for 10 testers, but I have got budget for only 5 testers. What should I d
o?
Since only 50% of resources are there . it is impossible to get the work @16 hrs/day. Besy
way to handle this situation is divide the work based on risk into- high,medium and low

77
 Manual Testing Very Important Questions and Answers

priority. Try to complete at least high and medium priority works by taking an additional
help from existing resources
8. U have tested the application ans it is released. Customer asks for some changes in the
proj and gives one week time to complete it. Out of the one week, 6 days is taken by the
developer to make changes . so u have only one day to test it. What will u do in this case
if u r following only manual testing?
In this dicusssion, I will prefer to consult the customer and request him to extend the date of
release for another 1 week, for thotough testing and fixing the defects that r found , so
that the quality product can be released.
If Customer does not agree,I prioritiseand test majot funcationalities. In case there are
critical defects found in major funcationalities I would recommend to extend the relase date
since relasing a quality prod is also as imp as relassing the prod on time.
9. I want to conduct completely security testing of my web based appl. Do u think u can handle
this?
I have very strong intention to learn new areas and I am sure security testing is one of very
challenging areas. Before I want to share my opinion I want to understand more about the
domain of the web based appl. If it is general web based application like chatting,social
networking,emailing etc. I am ready to take up the challenging and complete the same
successfully to my level best. If it is financial related application like banking appl,I would
suggest giving this responsibility for experienced security testers, who exclusively focuses on
security testing. I would be glad to participate with them to learn and contribute from my
side.
10. How do u test application without SRS?
I would 1st explore the screens and understand the project through exploratory testing. I
would also try to understand the business purpose of the proj to match business and proj
functionality. I even prefer to evaluate the similar projects and understand the variation
between my proj and other projects. Once I receive enough understanding about the proj I
try to test the proj screens for various sets of test data and report any issues. I will report to
the manager any missed features also to consider for future enhancement.
11. U found show stopper and your manager has asked u not to inform this with anyone? Do u
listen?
Yes .I do .bcoz my manager has a better idea about the project and business. But I also
expect transparency in the work. I draft an email about the issue identified and mail to
manger and cc to his boss. This helps to maintain the records of the issue identified and to
solve it later.
12. Writing test plan and test acse is a waste of time and money.ur views?
I disagree with this since test plan and test cases are very crucial for succesfull testing of the
proj. test plan is crucial since.
1. Test plan provides clear objective of testing
2. Test plan document many things required during testing like communication
method,bug tracking process, test stop criteria with out which testing goal will not
be fruitful.

78
 Manual Testing Very Important Questions and Answers

3. Test plan identify about risks and propose contingency plan much before and
ensure issues are handled effectively.

Test case are crucial since:

1. They guarantee that most imp and commonly used conditions of end use are
verified before prod is released.
2. Even a person with less exposure on the proj can also involve in test execution by
following the test cases drafted by experience resources.
13. How do u test projects that follow object oriented design?
I have tested many appl’s that r developed using OOPS lang’s like java,.net etc. being a
tester functional understanding of an application is essential for me. My testing focuses on
checking whether the application meets business req’s a specified in the SRS. It does not
matter which lang is used to develop the appl.
14. What is UML? How do u use in the project?
Uml is unified modeling lang used in designing obj oriented application with UML we can
design use case, sequence. diagrams and collaboration diagrams. Rational rose is one of the
familiar tools for uml design.
15. Roles and responsibilities u r currently handling?
In present organization as a Senior s/w eng I am involved in:
1. Understanding req’s from usecases provided in the SRS
2. Reviewing test plan
3. Designing test cases
4. Preparing traceability matrix
5. Reviewing test cases designed by peers
6. Executing the test cases
7. Genearating test reports
8. Reporting defects
9. Verifying the defects fixed by dev team and client
10. Sending daily and weekly status reports.
16. Why have u choosen testing as ur career?
I have choosen testing as my career bcoz
1. Testing is a challenging job
i. It requires deep understanding of domain
ii. It requires

………………………………………………………………………….

79
 Manual Testing Very Important Questions and Answers

Chapter 23

HR Questions

1. Can you please tell me about yourself?

1. I am Madhavi, having around 2 years of experience in the field of software testing.

2. Have involved in testing of various web based applications.
3. During my experience I have involved in designing the various test cases, reviewing test cases,
executing the test cases.
4. Different testing I have involved are requirements based functional tests, business process
based functional tests.
5. Apart from this I have also involved in some other testing like smoke testing, regression testing
UI testing, browser compatibility testing, system testing, cookie testing.
6. I have also involved in defect reporting and retesting.
7. I have also interacted with the developers, customers, business analysts time to time based on
the needs.

2. What are your long term and short term career goals?

In the next 7- 10 years, I want to grow as a test architect where I want to propose various testing
strategies for effective testing of complete software

In the next 1-2 years, I want to gain very good knowledge of the project and the domain. I will be part of
and contribute myself to the best of the project

3. Why do you want to leave your current position?

For better career prospectus or I am looking for a greater challenge.

Ex: small company gives these many opportunities to work on different tools, if I work in big company, I
can have more opportunities to grow as myself and can contribute myself to the organization’s growth

4. Tell me about your company?

ABC solutions is a private limited company ISO 9001 -2000 certified software development and testing
consulting company committed to developing effective software solutions with tangible results .It is the
seven years old company established in the year 2003 .Current strength of Organization is 120. It has
offices in India, US, Singapore etc.

Or

ABC IT solutions private Ltd is testing consulting company, where some employees are outsourced to
client’s locations and some employees work from our office off line. It is 4 year old company, established
in 2010.Currently we have 80 employees in our organization.

5 who is your CEO?

Our CEO is Mr. Murali. He has over 20 years of work experience with HP, Yahoo etc.

80
 Manual Testing Very Important Questions and Answers

6. How big is your organization?

We have 120 employees

7. What is your organization structure?

Note: This answer varies depends on your company

Managing director, CEO, technical group head, HR group head. The development manager, test
manager, team member

Or

Managing director, Test manager, test lead, senior test engineer, and junior test engineer

Diagram:

Managing director

CEO

technical group technical group head Hr Group head

head

Development test manager Development

Manager manager

team member 1 team member 2 team member 3

8. Where is your company located?

Our company is located in Jaya nagar 4th block, it is nearby coffee day.

9. I Stay close by .I did not find any software company there?

You are welcome to visit our office anytime

10. Whom do you report?

I report to my Project manager. Or Test Lead or to the assigned person

11. What is the e-mail id and phone number of your HR?

[email protected] Our HR manager is madhavi. I can share those details if necessary but I request you
to use this information of the releasing the offer. I hope you value my concerns

81
 Manual Testing Very Important Questions and Answers

12. Can I contact her for background verification?

Yes. You can

13. Can you provide a couple of references in your company?

Naveen is test lead, srikanth is my colleague.

14. Can you also give references in the client’s place you have worked?

I cannot share that as it was very clearly mentioned during induction program.

15 what is the e-mail id and extension number?

[email protected] .I don't have any extension number

16. Can I have your business card?

Sure. Have it.

Or Sure . Let me check whether I have.

or

I don't have business card with me right now

17 what is your salary can you know the net salary and gross salary ?

My package is 4 lakhs per annum no around 80 % is net take home just feel better erections mantrI I get
approximately 30 5000 rupees as take home salary

18 do you have p f account ?

you can answer yes or no notification no you can expect further queries

19 such a big company why you dont have pf account?

Answerpf the mail optional for increase the net take home salary so I dint uptodate but meaning in the
company is having pdfpf account. How do you draw your salary answer to bank true bank true?

21. Can you produce your form 16 ?

Should I can shoes shoesshoesshure a fraction icons I can.

22. Can you predict your bank statement?

should I can do you need both from 16 and bank statements .

23 do you know mathematics project of your company and ok about his or her designation

82
 Manual Testing Very Important Questions and Answers

stop saying yes yes I think I have seen him

24 what is your expected ctc ?

don't answer fast mustard say something like that it is a tough ? can you tell me the reason for this
position and in the most cases the interview is taken of god and he will tell you if not say that around 25
% hike

25. What is your notice period ?

as per the offer letter it is the two months but I think I can be delivered in 3 weeks

26. Newgenimmediately ?

I will try . But for sure in 3 weeks I can sign arrival train for 2 weeks www.disewap.com

27.why did you leave your last job?

28. Please explain why you have got a new employment history ?

answer. The employee is looking for any problem in your personal life that might become is headache if
he had you explain your gap hamstring but see that your answer does not create an impression that
your personality is if you cut your personal issues will disturb you while you're having your job
www.spoturtrain.com

29.what do co-workers say about you ?

Many times michaeljackson dead I am work early can never leave the car seat and tell ideas and work is
completed and my colleagues naveen said I am very applicable for any project related queries day have .
My contacts what does a person 99 percent of the times I am very analytical and understood the
customer business needs very well. I was successful in convincing him almost everybody that bag

30 what have you done to improve your knowledge in the last year ?

answer try to include your improvement activities that lead to the job sample answer is apart from the
models I want handley have also gained knowledge in the gift wrappers functionality with the help of my
colleagues who is apart of the functionality. I have also leyland have different tools lite browser for
adobe browserlab for browser compatibility testing .

31 are you applying for aadharjobs . ?

be honest also ashok that you are very interested to be a part of this organisation if after she is
approved bed sample answer. To be honest yes couple of interviews I have attended properties group
weather I am happy to work for this organization

32. Which company did you apply ?

I have attended for hp silk you still discussing for going on i'm assuming that if you can give me a good
offer shortly I will be joining you according to me would often does not mean only pay package it also
refers to my work opportunity to work on challenging assignments www.tatasky.com

83
 Manual Testing Very Important Questions and Answers

33.what do you want to work for this organisation ?

this may take some part and certainly should be based on amba research you have 100 nation infinitely
it is extremely important here and will be release some food related to your long term career google

34. How do you know anyone who works for us ?

be aware of the policy on the latest working for this organisation that can affect your answer even
though they are about your friends not relative always a better phone no if they ask how you know the
person who refer to tell that he is the friend's friend not known to you directly www.bhaktibhav.com

35.are you a team player ?

new couple of examples you are a team player sample answer is yes I am a team player there are many
times how are required to help new heights new employees news jaanI I have also help culex if they are
loaded with lots of work in the module

36 part how long would you expect to work

funmaza if you are held I would take it to be a long time are as long as we both feel I am doing good job

37. What is your philosophy towards work ?

interview is not looking for the long haul flower design sun here give short note to answer. Sample on
sarees. What is very important factor in anyone's life and wish you all the best to work it helps individual
and organization

38 what college experience are you especially proud of ?

portlet bracket make an extra curricular activities especially the ones that are relevant to your job
aptitude sample answer is I was the class representative for planning and organising how are are class
participation in the college level counselling activities we have won best team award winning over for
you sms college fest tatanano

39.what is dates you about co-workers ?

something which health organisation sample answer. Giving are necessary excuses without completing
the present work are simply complaining. Really understanding the problem.

40. What is tense would you bring to this job that other candidates may not ?

the implied arguing you the flore to tell to sell yourself for the job prepare well for this answer and
deliver it with confidence and sample answer is I don't want to compare and other doesn't have but I
can confidently say my ability to priya is my problem solving skills my ability to work under pressure
under my positive attitude ask him for the song are the streams strength for this job

41. Tell me about your dream job ?.

84
 Manual Testing Very Important Questions and Answers

This is the tricky ?s just give the money transfer as below... Answer is any job that gives me challenges
that gives good working environment that helps me to contribute for success of organisationiim part of
www.photo.com

42.what is more important to you the money out of work ?

man is always important part of what is the most important is if you do your best at work money
automatically will come to you what is true.

43. Tell me about your a problem you had with your supervisor

I never had any issues with any supervisor have worked so far. I always tried to undermine bath and alan
myself to give my best support achieve the product code he has .

44. Would you be willing to read locate if required ?

should be clear you should be clear andhra with your family. To the interview and be honest adidas..

45. Do you have any ?s for me ? android project your recruiting is in which domain ?

interview it may be a common phenomenon for the square you can have successfully handle some of
the e-commerce projects iphonedfu critical bugs in the e-commerce project work and I have also receive
the best distance learning about for the project you know if I am offered what kind of confusion you're
expecting from me no thanks for your time have enjoyed this kiss this discussion with you.

85
Manual Testing Very Important Questions and Answers

86
Manual Testing Very Important Questions and Answers

87