MARATHAHALLI BRANCH – CONTACT US—KARTHICK RAJA -- +91 75500 15337

1.What different types of manual testing are there?

Different types of manual testing are;


o Black Box Testing
o White Box Testing
o Unit Testing
o System Testing
o Integration Testing
o Acceptance Testing

2. What is alpha and beta testing?

These are the key differences between alpha and beta testing:

No. Alpha Testing Beta Testing

1) It is always done by developers at the software It is always performed by customers at

development site. their site.

2) It is also performed by Independent testing team It is not be performed by Independent

testing team

3) It is not open to the market and public. It is open to the market and public.

4) It is always performed in a virtual environment. It is always performed in a real-time

environment.
 MARATHAHALLI BRANCH – CONTACT US—KARTHICK RAJA -- +91 75500 15337

5) It is used for software applications and projects. It is used for software products.

6) It follows the category of both white box testing and It is only the kind of Black Box Testing.
Black Box Testing.

7) It is not known by any other name. It is also known as field testing.

3.What is the negative and positive testing?

Negative Testing: When you put an invalid input and receive errors is known as negative
testing.

Positive Testing: When you put in the valid input and expect some actions
that are completed according to the specification is known as positive
testing.

4.What is the benefit of test independence?

Test independence is very useful because it avoids author bias in defining

effective tests.

5.What are the different models available in SDLC?

There are various models available in software testing, which are the following:

o Waterfall model
o Spiral Model
o Prototype model
o Verification and validation model
o Hybrid model
o Agile model
o Rational unified process model[RUP]
o Rapid Application development [RAD]

6.How many test cases we can write in a day?

 MARATHAHALLI BRANCH – CONTACT US—KARTHICK RAJA -- +91 75500 15337

We can tell anywhere between 2-5 test cases.

o First test case → 1st day, 2nd day.

o Second test case → 3rd day, 4th day.
o Forth test case → 5th day.
o 9-10 test cases → 19th day.

Primarily, we use to write 2-5 test cases, but in future stages we write around 6-7 because,
at that time, we have the better product knowledge, we start re-using the test cases, and
the experience on the product.

7.How many test cases can we review per day?

It would be around 7 test cases we write so that we can review 7*3=21 test cases. And we
can say that 25-30 test case per day.

8. How many test cases can we run in a day?

We can run around 30-55 test cases per day.

9. Does the customer get a 100% bug-free product?

1. The testing team is not good

2. Developers are super
3. Product is old
4. All of the above

The correct answer is testing team is not good because sometimes the fundamentals of
software testing define that no product has zero bugs.

10. How to track the bug manually and with the help of automation?

We can track the bug manually as:

o Identify the bug.

o Make sure that it is not duplicate (that is, check it in bug repository).
o Prepare a bug report.
 MARATHAHALLI BRANCH – CONTACT US—KARTHICK RAJA -- +91 75500 15337

o Store it in bug repository.

o Send it to the development team.
o Manage the bug life cycle (i.e., keep modifying the status).

Tracking the bug with the help of automation i.e., bug tracking tool:

We have various bug tracking tools available in the market, such as:

o Jira
o Bugzilla
o Mantis
o Telelogic
o Rational Clear Quest
o Bug_track
o Quality center ( it is a test management tool, a part of it is used to track the bugs)
o A product based: In the product based companies, they will use only one bug
tracking tool.
o Service-based: In service-based companies, they have many projects of different
customers, and every project will have different bug tracking tools.

11. Why does an application have bugs?

The software can have a bug for the following reasons:

 MARATHAHALLI BRANCH – CONTACT US—KARTHICK RAJA -- +91 75500 15337

o Software complexity
o Programming errors
o If no communications are happening between the customer and the company, i.e.,
an application should or should not perform according to the software's needs.
o Modification in requirements
o Time pressure.

12. When do we stop the testing?

We can stop testing whenever we have the following:

o Once the functionality of the application is stable.

o When the time is less, then we test the necessary features, and we stop it.
o The client's budget.
o When the essential feature itself is not working correctly.

13. What is the difference between the traceability matrix and the
test case review process?

Traceability matrix Test case review

In this, we will make sure that each requirement In this, we will check whether all the scenarios are
has got at least one test case. covered for the particular requirements.

14. What is the difference between use case and test case?

Following are the significant differences between the use case and the test case:

Test case Use Case

It is a document describing the input, action, and expected response to It is a detailed description of
control whether the application is working fine based on the customer Customer Requirements.
requirements.
 MARATHAHALLI BRANCH – CONTACT US—KARTHICK RAJA -- +91 75500 15337

It is derived from test scenarios, Use cases, and the SRS. It is derived from BRS/SRS.

While developing test cases, we can also identify loopholes in the A business analyst or QA Lead
specifications. prepares it.

15. What is a test plan and what does it include?

A test plan stores all possible testing activities to ensure a quality product. It gathers data
from the product description, requirement, and use case documents.

The test plan document includes the following:

 Testing objectives
 Test scope
 Testing the frame
 Environment
 Reason for testing
 Criteria for entrance and exit
 Deliverables
 Risk factors

16. What is agile testing and why is it important?

Agile testing is a software testing process that evaluates software from the customers’
point of view. It is favorable as it does not require the development team to complete
coding to start QA. Instead, both coding and testing go hand in hand. However, it may
require continuous customer interaction.

17. What is the purpose of the end-to-end testing?

 MARATHAHALLI BRANCH – CONTACT US—KARTHICK RAJA -- +91 75500 15337

End-to-end testing is a testing strategy to execute tests that cover every possible flow of
an application from its start to finish. The objective of performing end-to-end tests is to
discover software dependencies and to assert that the correct input is getting passed
between various software modules and sub-systems.

18. What are the different types of functional testing?

Functional testing covers the following types of validation techniques:

 Unit testing
 Smoke testing
 UAT
 Sanity testing
 Interface testing
 Integration testing
 System testing
 Regression testing

19. What do you understand about STLC?

Software testing life cycle (STLC) proposes the test execution in a planned and
systematic manner. In the STLC model, many activities occur to improve the quality of
the product.

The STLC model lays down the following steps:

1. Requirement Analysis
2. Test Planning
3. Test Case Development
4. Environment Setup
5. Test Execution
6. Test Cycle Closure
 MARATHAHALLI BRANCH – CONTACT US—KARTHICK RAJA -- +91 75500 15337

20. In software testing, what does a fault mean?

A fault is a condition that makes the software fail to execute while performing the
considered function.

21. Difference between bug, defect, and error.

A slip in coding is indicated as an error. The error spotted by a manual tester becomes a
defect. The defect which the development team admits is known as a bug. If a built code
misses on the requirements, then it is a functional failure.