Scribd
Upload
16 views4 pages

Software Testing

Software testing evaluates application functionality to ensure it meets expectations, involving both Quality Assurance and Quality Control to identify defects. Manual testing is performed without tools, while automation testing utilizes tools like Selenium for efficiency. Testing is crucial for business success, as undetected bugs can lead to negative user experiences and financial losses.

Uploaded by

iam.sharanyv
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
16 views4 pages

Software Testing

Software testing evaluates application functionality to ensure it meets expectations, involving both Quality Assurance and Quality Control to identify defects. Manual testing is performed without tools, while automation testing utilizes tools like Selenium for efficiency. Testing is crucial for business success, as undetected bugs can lead to negative user experiences and financial losses.

Uploaded by

iam.sharanyv
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 the process of evaluating the functionality of an application


to ensure it behaves as expected.
● It involves both Quality Assurance (QA) and Quality Control (QC) to maintain
software quality.
● The main purpose is to identify bugs or defects in the application.
_____________________________________________________________________________________-

WHAT IS MANUAL TESTING

● Testing the Functionality of an Application Without Using Any Tool is Called


Manual Testing.
● Example:
● If I Start the Bike Using Kicker, it is Called Manual Testing.
● If I Turn On TV Manually, it is Called Manual Testing.

____________________________________________________________________________________

WHAT IS AUTOMATION TESTING

● Testing the Functionality of an Application Using Tools like Selenium, OTP, UFT,
Silk Testing.
● Example:
● Starting the Bike Using Self Start is Called Automation Testing.
If I Turn On the TV Using a Remote, it is Called Automation Testing.

Here, Remote is Selenium; Battery is Java.

______________________________________________________________________________________
WHY DO WE WANT TESTING

● Every Application is Created for a Business Purpose.


● If Any Bug is Found by the Users, It Will Create a Negative Impact
Across the Market.
● Users Will Not Use the Application; It Will Affect the Business.
● For That, Testing Is Impor tant.
● If I am Using an ATM Application to Withdraw Money 1000.
● I Got a Deduction Message But Money Was Not Dispensed.
● If It Happens for Many Users, People May Stop Using the
Application.
● It Will Cause Loss for the Bank.
● For That, Testing is Impor tant.
● For example, if an e-commerce website's checkout process isn't
tested properly,
● customers might face issues like incorrect billing or failed
payments, leading to a poor user experience and lost sales.
● Testing helps identify and fix these issues early, ensuring the
application is reliable and meets user needs."

______________________________________________________________________________________

Scenario

● Testing an Application in All Possible Ways is Called Scenario


● Two Types of Scenario Exist
● Positive Scenario
● Negative Scenario
● Testing an Application with Valid or Expected Data or Input is Called Positive
Scenario.
● Testing an Application with Invalid or Unexpected Data or Input is Called
Negative Scenario.
● If Needed to Find Both Bugs, We Need to Write More Scenarios.
● If We Miss a Scenario, We Will Miss Bugs.
● If Scenario Exists, Bugs May or May Not Exist.

______________________________________________________________________________________

What is Test Case

● Test Case is a Document Which Contains a Step-by-Step Procedure to Test the


Application.
● To Write Test Cases, We Use Templates.
● We Are Having Different Types of Templates; It Varies from Company to
Company and Project to Project.

_____________________________________________________________________________________-

When We Write the Test Case

While Developers Are Developing the Application, We Write the Test Case.

There Are Two Stages of Test Case:

1.) Test Case Preparation or Test Case Writing

2.) Test Case Execution.

1.) Test Case Preparation or Test Case Writing

● Under Test Case Preparation, We Will Fill the Following Sections like Header,
Body, Footer.
● In the Body Section, We Will Fill the Expected Result.
2.) Test Case Execution

● After the Application Is Given by the Developer, We Have to Fill the Actual Result,
Status, Comment.
● We Fill Actual Result Based on the Application.
● - When the Actual Result and Expected Result Match, Status Will Be Pass; Else
Fail, Then It is a Bug

______________________________________________________________________________________

Difference Between Scenario and Test Case:

● Scenario
● Describes the possible ways to test an application.
● Indicates *what* to test.
● It Is a high-level document.
● Takes less time to write.
● Does not contain negative steps.
● Does not specify where the exact defect is present.

● Test Case
● Provides a step-by-step procedure for testing an application.
● Specifies *how* to test.
● It Is a low-level document.
● Takes more time to write.
● Includes negative steps.
● Pinpoints the exact location of any defect.

______________________________________________________________________________________

You might also like