Scribd
Upload
352 views

Manual Testing Assignment

The document discusses various topics related to manual software testing including tester qualities, why testing is important, different types of testing, test cases, test plans, traceability matrices, requirements, test strategies, test methodologies, and defect management. Specifically, it provides questions to help explain concepts like the importance of testing software before delivery to identify bugs, different testing types like unit and integration testing, how to write effective test cases and test plans, using traceability matrices to track requirements, and properly managing defects found during the testing process.

Uploaded by

Bao Truong Hoang
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
352 views

Manual Testing Assignment

The document discusses various topics related to manual software testing including tester qualities, why testing is important, different types of testing, test cases, test plans, traceability matrices, requirements, test strategies, test methodologies, and defect management. Specifically, it provides questions to help explain concepts like the importance of testing software before delivery to identify bugs, different testing types like unit and integration testing, how to write effective test cases and test plans, using traceability matrices to track requirements, and properly managing defects found during the testing process.

Uploaded by

Bao Truong Hoang
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 9

Manual Testing Assignment

Tester Qualities
1. What qualities testers should have?
2. As a tester, what qualities do you have? Provide with examples to justify
your qualities?
3. Describe what you would like to do in a new job as a Software Tester?
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?
=> It can help you
 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?
Acceptance testing is often the responsibility of the customers or users of a
system; other stakeholders may be involved as well.
The goal in acceptance testing is to establish confidence in the system, parts
of the system or specific non-functional characteristics of the system.
Finding defects is not the main focus in acceptance testing.
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?

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?
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?
6. What is called a good Test Case? What is a bad Test Case?
7. What are guidelines for writing Test Cases?
8. What is Test Data? Why is it important?
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:
 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?
2. Traceability matrix is useful? How? Describe with Example with any
application?
3. Develop Traceability Matrix for Flight Reservation Application?

Requirement
1. What’s full form of SRS?
2. Why SRS is important in Manual Testing?
3. What is Use Cases?
4. Design 5 different Use Cases?
5. What are Non-functional Requirement in SRS?
6. Design an Use Case Diagram? Describe briefly.

Test Strategies
1. What is Test Strategies? Importance.
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?
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?
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.

You might also like