Scribd
Upload
18 views4 pages

Manual Interview

Uploaded by

Prashant KalePatil
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
18 views4 pages

Manual Interview

Uploaded by

Prashant KalePatil
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

 What is Software Testing?

Software Testing is a method to check whether the actual software product


matches expected requirements and to ensure that software product
is Defect free.

 Why software testing is important?

It identifies any issues & defects with the written code so they can be fixed before
the software product is delivered. Improves product quality. The goal of software
testing is to find errors, gaps, or missing requirements in comparison to the actual
requirements.

 What is the difference between bug and defect

A bug is an error in the software that causes it to malfunction. The functionality


of an application not working as per the customer’s requirement is known as a
defect. The bug is found by the testing team. The defect is found by the
development team.

 What Is Unit Testing?

Unit Testing is the process of checking small pieces of code to deliver information
early & often.

 What is System Testing?


System Testing is a level of testing that validates the complete & fully integrated
software product.

 What is API testing?

API (application programming interface) testing is performed without having its


GUI. It is a part of integration testing that determines whether the APIs
meet the testers' expectations of functionality, reliability, performance,
and security.

 Test Case For WhatsApp Status

 Check whether the user can set DP or not.


 Check whether the user can update the DP or not.
 Check whether the user can set the status or not.
 Check whether the user can update the status or not.
 Check the Status Privacy functionality
 Check the user is able to see status privacy options on the screen.
 Check the status privacy functionality with My Contacts options
 Check the status privacy functionality with My Contacts except for options
 Check the status privacy functionality with the Only share with options
 Check whether the recent updates are displayed or not.
 Check the user is able to see the number of unseen status notifications in
WhatsApp Status.

 What is the meaning of acceptance testing?

Acceptance testing is a quality assurance (QA) process that determines to what


degree an application meets end users' requirement/expectations.

 Functional testing and non-functional testing types

Functional testing ensures that the functions and features of the application work
properly. Non-functional testing examines other aspects of how well the
application works.

Non- Functional Testing is also categorised into 8 subtypes – [CCRII_SPG]

1. Compatibility Testing
2. Configuration Testing
3. Recovery Testing
4. Installation Testing
5. Intersystem Testing
6. Sanitation Testing
7. Parallel Testing
8. Globalization Testing

Functional Testing is also categorised into 6 subtypes – [BIE_BSC]

1. Behaviour Coverage Testing


2. Input domain Testing
3. Error handling Testing
4. Back-end coverage Testing
5. Service level Testing
6. Calculation based Testing

 What is Test scenarios & Test cases.

A test scenario is a set of manual or automated test cases that helps determine
the positive and negative project characteristics. It provides an overview of what
needs to be tested by a QA company. The main purpose of a test scenario is to
check the entire system performance from the end-user point of view

Test case: It is a set of actions to verify the specific features of the products.
 Difference Between Verification & Validation.

VERIFICATION VALIDATION

Here we check documents, design, It includes testing & validation of


code & program. the actual product.
Verification doesn’t involve code Validation involves code Execution.
execution.
Verification checks whether the Validation checks whether the
software confirms a specification. software meets the requirements &
expectations.
Verification finds the bugs early in Validation finds the bugs that
the development cycle. verification cannot catch.
Verification process comes before Validation process comes after
validation. verification.
QA team does verification & make With the involvement of testing
sure that the software is as per the team validation is executed on
requirement in the SRS document. software code.

 What is the difference between positive & negative testing

Positive testing determines that our application works as expected. If an error is


encountered during positive testing, the test fails.

Negative testing ensures that our application can gracefully handle invalid input
or unexpected user behaviour.

 What is the difference between static & negative testing

Static Testing is a type of software testing in which software application is tested


without code execution. It is basically performed in SDLC.

Dynamic Testing is a type of software testing in which software application is


tested with code execution. It checks for functional behaviour of software system,
memory/cpu usage & overall performance of the system.

 Static testing is about the prevention of defects whereas Dynamic testing


is about finding and fixing the defects.
 Static testing does the verification process while Dynamic testing does the
validation process.

 Drawbacks of Manual Testing


1. Manual Testing requires more time or more resources, sometimes both Time
and Resources.
2. Less Accuracy
3. Executing the same tests, again and again, is time taking process as well as
Tedious.

 Advantages of Manual Testing


1. No Environment Limitations.
2. Programming Knowledge is not required.
3. Manual testing allows for human observation, which may be more useful to find
potential defects.

 What is meant by waterfall model.?

The Waterfall methodology — also known as the Waterfall model is a linear


sequential development process that flows like a waterfall through all phases of a
project (Analysis, Design, Development & testing) with each phase completely
wrapping up before the next phase begins.

You might also like