Scribd
Upload
74 views4 pages

Manual Testing Faqs

Integration testing involves testing combined parts of an application to determine if they function together correctly. A stub is a temporary component that sends responses, while a driver is a temporary component that integrates and stores results from two components. Traceability matrices map test cases to requirements in a table to ensure all functionality is covered. Prioritizing high priority test cases allows proceeding with testing initially. Reviews involve peer evaluation of test artifacts. Defects are issues found in testing, bugs are issues in production, and errors occur during development. Alpha testing is conducted internally while beta testing involves external users. User acceptance testing is final testing by end users before release. Non-functional testing evaluates performance, security, compatibility and other non-functional requirements.

Uploaded by

kkiran2590
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
74 views4 pages

Manual Testing Faqs

Integration testing involves testing combined parts of an application to determine if they function together correctly. A stub is a temporary component that sends responses, while a driver is a temporary component that integrates and stores results from two components. Traceability matrices map test cases to requirements in a table to ensure all functionality is covered. Prioritizing high priority test cases allows proceeding with testing initially. Reviews involve peer evaluation of test artifacts. Defects are issues found in testing, bugs are issues in production, and errors occur during development. Alpha testing is conducted internally while beta testing involves external users. User acceptance testing is final testing by end users before release. Non-functional testing evaluates performance, security, compatibility and other non-functional requirements.

Uploaded by

kkiran2590
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

1. Integration Testing?

 Ans: testing of combined parts of an application to determine if they function together


correctly. The 'parts' can be code modules, individual applications, client and server
applications on a network, etc. This type of testing is especially relevant to client/server
and distributed systems.

2. What is stub & Drivers?


Ans.

Stub Driver
A Stub is a temporary component that A driver is also a temporary component which will
sends response to other component. It is integrate two components and stores the result. It is
called component. calling component.

3. Traceability matrix? Forward and Backward Traceability matrix approaches with examples?
Ans: the mapping of use cases and test cases in the form of rows and columns is known as
traceability matrix.

4. How can u come to know that u have covered all functionality?


Ans: By using the traceability matrix we will ensure whether v have covered all functionality.

5. I have given 1200 test cases for 1 day. How u will precede Testing?
Ans: Initially ill prioritize all the test cases and ill execute only the high priority test cases.

6. Reviews (Peer reviews, walkthroughs, inspections, formal reviews, informal reviews)?

Ans: Reviews are nothing but the opinion of colleagues on our test cases.

Walkthrough(informal
7. Peer Reviews reviews) Inspections (formal reviews)
these are nothing This is an informal meeting An inspection is more formalized than a
but the personal for checking og our test 'walkthrough', typically with 3-8 people including
reviews of all our cases.no preparation is a moderator, reader, and a recorder to take
team members. required for this. notes on our test cases.
Waterfall model – Agile model – V model

.
8. Defect – Bug – Error?
Error Defect Bug
An error is encountered by a devloper in A Defect is faced by tester in A Bug is faced by Advisor
development envirement. testing envirement in prod envirement

9. Alpha testing & Beta Testing?


Alpha and Beta testing concepts are different from Product based company
and a Service based company.
Company Type Alpha Testing Beta Testing
testing done by the
tester by
testing which is done generating the
at the customer's
Product based developer's site by environment
company the testers .
the process of giving
the product to
customers and let
them do the testing
testing conducted by at their
Service based customers at environment.
company Developer's site.

10. User Acceptance Testing?

Testing
Type Why When
User Acceptance
Usually the end users who will be using the applications test the Testing is often the
User application before ‘accepting’ the application. final step before
Acceptanc This type of testing gives the end users the confidence that the rolling out the
e Testing application being delivered to them meets their requirements. application.

11. Non functional Testing’s?


Generally we are not involved in the Non functional testing’s.
Non
functional
Testing Types Description
Performance testing is conducted to evaluate the compliance of the system with the
performance requirement specifications with acceptable response times and resource
1.Performanc utilization (memory, processor, network).Load and stress testing are types of
e Testing performance testing with distinct goals.

1.1 Load Load Testing is nothing but , Increasing the load level from normal to High .nd
Testing checking system performance at maximum load as per client requirement.
Load means, the number of concurrent users acting on the application.
Load testing is done to determine the capability of the system to handle the
anticipated number of concurrent users without much degradation in system
performance.
1.2 Stress Stress testing is conducted to determine the amount of load the system can handle
testing before breaking down or to identify the peak load handled by the system.
2.Data
Volume Volume testing refers to testing a software application performance with a certain
Testing amount of data.
3.Security It is a process to determine that an information system protects data and maintains
testing functionality as intended.

12. Functional Testing?

13. Web Testing?


Web testing is the name given to software testing that focuses on web applications. Complete
testing of a web-based system before going live can help address issues before the system is
revealed to the public.
Web security testing tells us whether Web based applications requirements are met when they
are subjected to malicious input data.

14. Unit Testing? Unit testing techniques?

Unit Testing is part of white box testing .This is nothing but code testing. Checking the code by
module wise & executing unit test cases by individual module.

15. Block box Testing? Block box Testing Techniques?


Block box testing is nothing but functional testing
Typical black box test design techniques include:
 Decision table testing
 Pair wise testing
 State transition tables
 Equivalence partitioning
 Boundary value analysis

16. Defect life cycle


The different phases in defect life cycle include:

Open: New defect reported by a tester (customer, tech support rep, etc).

Assigned: Defect assigned to a developer to be analyzed/repaired (not in book's version)

Fixed: developer has implemented a fix

Resolved/Closed: Tester verifies that fix corrects the bug

Deferred: Defects that are being put off until a future release

Review: Waiting for decision by CCB

17. What are the challenges u faced?

18. Importance of Deferred?

19. What are quality standards u will think to improve testing?

20. Agile – V Model?

21. Retrospective call?


It is the call made by client before the release in which every tester will participate.In this client will
ask often ‘what went well’ etc..

You might also like