Manual Testing Assignment

Tester Qualities
1. What qualities testers should have?
Qualities of a good tester
 You Understand Priorities
 You Ask Questions
 You Can Create Numbers Of Ideas
 You Can Analyze Data
 You Can Report Negative Things In A Positive Way
 You Are Good At Reporting
 You Are Flexible To Support Whenever It’s Required
 You Are Able To Co-Relate Real-Time Scenarios To Software Testing
 You Are A Constant Leaner
 You Can Wear End User’s Shoes

2. As a tester, what qualities do you have? Provide with examples to justify

your qualities?
The qualities do Tester have
 Positive Attitude
 Good Communication
 Multi-Tasking Abilities
 Quick Learner
 Passion For Testing
 Team Player
 Think And Act As An End-user
 Analytical Abilities
 Be An Inspiration And A Role Model
 Practice Empathy
For example: A brand new application that is just being integrated as a
trial run. Would you just come crumbling on it, wage a war and report that
 it is fit for nothing? Or would you test it sympathetically and try to find
problem areas so you can help the developers aid further improvement?

Let’s look at it from a real-world example perspective. You just finished

building a chair. Would you jump into it or sit carefully the first time? The
later, isn’t it? After you are confident it holds you then start adding unusal
weights etc.

Testing in the initial stages has to subtle, slow and kind. Also, empathy can
help you be a better team player – not only within your team but with
external teams as well. When in doubt, be kinder than you need to be. I
hope this list gives you an idea as to which area you need to work to be a
better software tester.

3. Describe what you would like to do in a new job as a Software Tester?

 Get ready with learning basic principles of Software Testing  This will
help you gain practical knowledge and will fortify the testing concepts
you have learned.
 Next, you proceed in some tutorials to get very strong knowledges as
well.
 Once you are through with all the practical, you may consider taking a
certification. I recommend ISTQB.

4. Why a Tester needs to interact with various IT departments?

Why Testing Is Important?

1. Why is Testing important? Justify with few good examples?
Testing is important because
 To identify defects/bugs before the delivery to the client.
 To reduce flaws in the component or system.
 It makes the software more reliable and easy to use.
 Increase the overall quality of the system.
 Example: assume you are using a Net Banking application to transfer the
amount to your friend's account. So, you initiate the transaction, get a
successful transaction message, and the amount also deducts from your
account. However, your friend confirms that his/her account has not
received any credits yet. Likewise, your account is also not reflecting the
reversed transaction. This will surely make you upset and leave you as an
unsatisfied customer.

2. What happen if you not test software properly? Provide few examples and
problems occurred due to not testing enough?

3. How rigorous testing helps IT companies?

Rigorous testing: of systems and documentation can help to reduce the risk of
problems occurring during operation and contribute the quality of the software
system, if the defects found are corrected before the system is released for
operational use.

4. Why Testing is important in Software Industry?

Because they can be identified any bugs or errors at the early and fixed before
the software product is delivered.
 Helps in saving money
 Security
 Quality of the product
 Satisfaction of the customer
 Enhancing the development process
 Easy while adding new features
 Determining the performance of the software

5. What are the advantages of starting early testing in SDLC?

 This helps to capture and eliminate defects in the early stages of SDLC.
(Example: requirement gathering and design phases)
 An early start to testing helps to reduce the number of defects and
ultimately the rework cost in the end.
6. Can testing be 100% if not then why?

7. Provide various justification for separating software testing from software

development job? Why not software developers should conduct complete
testing rather than companies pay separately to software testers?

Different Types Of Testing

1. What are the different types of Testing?
Refer this answer in the question number 2

2. Explain each in not more than 5 sentences:

 Unit Testing
 Integration Testing
 Alpha Testing
 System Testing
 Usability Testing
 Cross Browser Testing
 Multi Platform Testing
 Performance Testing
 Security Testing
 User Acceptance Testing (UAT)
 Beta Testing

3. What is Functional Testing? List various testing which come under this
category?
Validate the software system based on the requirement of the client, a
document called a software specification or Requirement Specification is
used as a guide to test the application.

4. What is Non Functional Testing? List various testing which come under this
category?
 Validating various non-functional aspects of the system such as user
interfaces, user-friendliness, security, compatibility, Load Stress, and
Performance.

5. How Acceptance testing is importance? Who does acceptance Testing? What

we do in this testing?
The importance of acceptance testing:
 Validates that business requirements are met based on the in-scope user
stories.
 Reduces the risk of defects being identified in production
 End users will gain skills and confidence while using the new system
prior to go live

Who does acceptance testing: only the member of the organization (who
developed the Product) perform the testing. These members are not directly a
part of the project (Project managers/leads, developers, testers). Management,
Sales, Support teams usually perform the testing and provide feedback
accordingly.

What we do in this testing?

 Confirm that the software product can perform all the business
functions.
 Confirm that the software product is usable from the end-users
perspective.
 Certify that the software product is ready to move to production

6. List five key differences Smoke Testing Vs Sanity Testing?

Smoke Testing Sanity Testing
Smoke testing is performed by either Sanity testing is normally performed
developers or testers. by testers.
Smoke testing may be stable or
unstable. Sanity testing is stable.
Smoke testing is done to measures Sanity testing is done to measures
the stability of the system/product the rationality of the system/product
by performing testing. by performing testing.
Smoke testing is used to test all over Sanity testing is used in the case of
function of the system/product. only modified or defect functions of
system/products.
Smoke testing can be performed Sanity testing is commonly executed
either manually or by using manually, not by using any
automation tools. automation approach.
Smoke testing is performed when Sanity testing is conducted after the
new product is built. completion of regression testing.

7. Define Manual Vs Automated testing?

Manual Testing is the process of testing the software manually.

We use human resources to perform testing then we can consider the

testing as Manual. In other words, in this type, we execute test cases
manually. The skills, knowledge, and experience of the testers play an
important role in Manual Testing.

Usage of automation tools for executing test cases is known as Automation

Testing. It is a type of testing for which we need resources with the
knowledge of scripting, etc.

Selenium, QTP, UFT are some examples of automation tools. Selenium

comes with C#, JAVA, Pearl, PHP, Python, and Ruby. Hence having
knowledge of any of these listed languages will work.
8. List as many differences as you can between white box testing and black
box testing?
White Box Testing Black Box Testing
It is a way of testing the software in It is a way of software testing in
which the tester has knowledge which the internal structure or the
about the internal structure or the program or the code is hidden and
code or the program of the nothing is known about it.
software.
It is mostly done by software It is mostly done by software
developers. testers.
It is structural test of the software. It is functional test of the software.
It is the behavior testing of the
It is the logic testing of the
software.
software.

This type of testing of software is This testing can be initiated on the

started after detail design basis of requirement specifications
document. document.
It is mandatory to have knowledge No knowledge of programming is
of programming. required.

Test Cases
1. What is a Test Case?
Test case: is a set of pre-conditional steps to be followed with input data and
expected behavior to validate the functionality of a system.

2. List out level of Test Cases? What are fields of a Test case Template?
The level of test cases
 Functionality Test Cases
 User Interface Test Cases
 Performance Test Cases
 Integration Test Cases
 Usability Test Cases
 Database Test Cases
  Security Test Cases
 User Acceptance Test Cases

The fields in test case template

 Test case ID
 Test case description
 Severity
 Priority
 Environment
 Build version
 Steps to reproduce
 Expected results
 Actual results

3. Write test cases for Gmail Login? Give at least 5 examples?

4. Design 3 positive Test cases and 3 negative test cases

regarding: http://newtours.demoaut.com

5. What problems you face in writing test cases?

 Lack of communication
 Missing documentation
 Diversity in Testing Environments
 Inadequate Testing

6. What is called a good Test Case? What is a bad Test Case?

Good test case: a test case that has a high priority of catching defects is
called a good test case.

Bad test case: a bad test fails on random or desirable change: randomly,
whenever someone refactors the code with no behavior change, when the
environment it is executed in changes, when a new feature is introduced, etc.
Too many bad tests means that development wastes time fixing tests any time
they want to get anything done.
7. What are guidelines for writing Test Cases?
 Consider Test Cases based on Risks and Priorities
 Remember the 80/20 rule
 Make sure your test cases can be completed by others when necessary
 The “Good enough” test case
 Create test cases like you are running a marathon not a sprint
 List your tests before you write them
 Classify test cases based on business scenarios and functionality
 Not too long or too short
 Test-drive your tests
 Run your tests regularly to keep them relevant

8. What is Test Data? Why is it important?

Test Data is the input given to a software program during test execution. It
represents data that affects or affected by software execution while testing.
Test data is used for both positive testing to verify that functions produce
expected results for given inputs and for negative testing to test software
ability to handle unusual, exceptional or unexpected inputs.

The data may be in any form like:

 System test data
 SQL test data
 Performance test data
 XML test data

Test data is important

 Test data to check that the outputs are derived correct.
 Test Data varied for different scenarios in testing(valid/invalid)
 Test Data helps the developers to find the problem during fixes.
 test data might be useful for other users/developers that what the
system gave for the given inputs.
  Test Data may be used in a confirmatory way, typically to verify that a
given set of input to a given function produces some expected result.
9. Develop Test cases for Flight Reservation Application?
(Use standard guidelines to write your test cases. Cover all sections
provided in SRS).

Test Plan
1. What is Test plan ? What are the Contents of a Test Plan? Describe each.
Test planning activities for an entire system or part of a system may
include:
Test plan: it is a document describing the scope, approach, resource, and
schedule of testing activities. It identifies test items, features to be tested,
testing tasks, who will do each task, and any risks requiring contingency
planning.
 Determining the scope and risks and identifying the objectives of testing
 Defining the overall approach of testing, including the definition of the
test levels and entry and exit criteria
 Integrating and coordinating the testing activities into the software life
cycle activities (acquisition, supply, development, operation and
maintenance)
 Making decisions about what to test, what roles will perform the test
activities, how the test activities should be done, and how the test results
will be evaluated.
 Scheduling test implementation, execution and evaluation
 Assigning resources for the different activities defined.
 Defining the amount, level of detail, structure and templates for the test
documentation
 Selecting metrics for monitoring and controlling test preparation and
execution, defect resolution and risk issues.
 Setting the level of detail for test procedures in order to provide enough
information to support reproducible test preparation and execution.
2. Write an example of a Test Plan?

3. Develop Test Plan for Flight Reservation System Application? Make sure you
cover all the sections and it should looks like professional document?

Traceability matrices
1. What is Traceability matrices? How to use it?
A Traceability Matrix is a document that co-relates any two-baseline documents
that require a many-to-many relationship to check the completeness of the
relationship.
It is used to track the requirements and to check the current project
requirements are met.

How to use it

 Define your goals.

 Gather Your Artifacts
 Create a Traceability Matrix template in Excel
 Copy and Paste Requirements From Your Requirements Document
 Copy and Paste Test Cases From Your Test Case Document
 Copy and Paste Test Results and Issues
 Update the Traceability Matrix

2. Traceability matrix is useful? How? Describe with Example with any

application?
Traceability helps you measure your team’s success effectively, by letting
you check if the most important business needs have been met.
 Traceability matrices make it easy for you to track the relationship between
requirements, code, test cases and release plans. You now have control of
and the ability to prioritize your team’s time towards the most important
tasks at any given point of time.

3. Develop Traceability Matrix for Flight Reservation Application?

Requirement
1. What’s full form of SRS?
 Software Requirement Specification (SRS)

2. Why SRS is important in Manual Testing?

An SRS document helps team members from different departments stay
on the same and make sure all the requirements are fulfilled. This
document also allows minimizing software development expenses and
time. 

3. What is Use Cases?

A use case is a written description of how users will perform tasks on your
website.  It outlines, from a user’s point of view, a system’s behavior as it
responds to a request

4. Design 5 different Use Cases?

 Activity Diagram
 Sequence Diagram
 Use Case Diagram
 Class Diagram
 Component Diagram

5. What are Non-functional Requirement in SRS?

Non-functional requirements in an SRS document specify the quality attributes
of a software system, such as responsiveness, usability, and reliability.
6. Design an Use Case Diagram? Describe briefly.

Use Case Diagram is a graphical depiction of a user's possible interactions with

a system. A use case diagram shows various use cases and different types of
users the system has and will often be accompanied by other types of diagrams
as well. The use cases are represented by either circles or ellipses.

Test Strategies
1. What is Test Strategies? Importance.
Test Strategies
Checking whether the application is compatible with different software and
hardware environments or not is called compatibility testing.
Importance
Test strategy plan always helps to clearly plan and mitigate risks involved in
the project. Agile teams can capture and document all high-level activities to
complete test execution on time without any issues.

2. Discuss a Test Strategies on object-oriented software?

3. What are the different Test environment, infrastructure and tools?

Test Methodologies
1. What is Agile Methodology?

2. How Scrum Works? Describe each components.

3. What is Product Backlog? Design a Sample.

4. What are advantage and disadvantage Agile Scrum?

5. How Waterfall model work? Define each Phase.

6. Why Waterfall model is harmful?

Defect Management
1. What is software defect or bug?
A software bug is an error, flaw or fault in a computer program or system
that causes it to produce an incorrect or unexpected result, or to behave in
unintended ways.
2. List 10 different defects with example which you encountered in your
previous projects?
3. What are the different causes of Defects i.e why defects occur?
4. Define Defect Life Cycle?
5. What is defect  or bug report?
Defect report, is a document that identifies and describes a defect detected
by a tester. The purpose of a defect report is to state the problem as clearly
as possible so that developers can replicate the defect easily and fix it.
6. Have you developed bug report? If yes, then explain what are various
sections did you include in your bug report?
7. How was defect management process implemented in your company?
8. Once QA found defect, what s/he does with that defect?
Case1: When defect was found on Production but not during QA environment.
1) Reproduce the problem on Production and QA environment. If the
problem is occurring only on Production then it may be due to
configuration issue.
2) On the other side if it is occurring on QA environment then check the
impact of that issue on the application. Investigate the issue to find out
that how long that defect has been around.
 3) Determine the fix of ticket and list out the areas where can put more
impact.
4) If the issue is impacting more customers then apply the fix and deploy it
on QA environment.
5) Testing team should focus on testing all the regression scenarios around
the fix.
6) If the applied fix works fine then it should be deployed to production and
post release sanity should be done so that it should not occur again.
7) Do a retrospection meeting.

Case2: When defect is found on QA environment.

Test Effort Estimation

1. What is Test Effort Estimation?
 Test effort estimation is the process of predicting effort for testing the
software.
 Test Estimation is a management activity which approximates how long
a Task would take to complete.
 Many factors such as Resources, Times, Human Skills, Cost.
2. Design a Test Effort Estimation?
Following is the 4 steps process to arrive at an estimate:
1) Divide the whole project into the smallest tasks.
2) Allocate each task to team members.
3) Estimate the effort required to complete each task.
4) Validate the estimation.