a ppt describes on the QA Workshop

1. PRESENTED BY
Rahul Jani
Dharmik Yadav
QA Workshop

2. What Is QA ?
- A Procedure To Maintain Quality & find
out Defect to Fix it.
- Software Testing Is a Part of software
development process.
- Software Testing Is an Activity to detect
and identify the defects in the software.

3. What is the Requirement of QA ?
To avoid Damage of financial , physical and every
factor Assure That your product properly fits with user
expectations.
#Advantages Of QA
 Ensuring Customer
Satisfaction
 Minimizing Costs and Risks
 Continuous Improvement
 Increasing Productivity

4. How its work in IT Company ?
QA(Quality Assurance) QC(Quality Control) Testing
QA plays a Major role in the early
identification and prevention of
product defects.
• It is the technique of managing
quality.
• It is process oriented.
QC involves thoroughly examining
the software for any issues or
glitches after it has been developed.
• It is the technique to verify quality.
• It is product oriented.
Testing is the primary activity of
detecting and solving technical
issues in the software.
• It includes activities that ensure
the identification of
bugs/errors/defects in a software.
• Product-oriented activities

5. What is Software Quality
1 Max Bugs Fixes
3 Delivered On Time
2 Compatibility
4 Meets Requirements and or / Expectations
5 Security

6. SDLC - Software Development Life Cycle
1
Actual Coding Phase Where Software is Built
4
Testing
Through Examination to ensure that the
Software meets the defines Requirements
5 Deploy / Maintenance
Rolling out Software for User access and the Providing
Support.
Requirements Analysis
Gathering requirement and analysing
2
Design
Design of the software is created
3 Development

7. STLC – Software Testing Lifecycle
1
Here, detailed test cases are defined and developed. The
testing team also prepares the test data for testing.
4
Test Environment Setup
It is a setup of software and hardware for
the testing teams to execute test cases.
5 Test Execution
It is the process of executing the code and
comparing the expected and actual results.
Requirements Analysis
QA team understands the requirement in terms of what
we will test & figure out the testable requirements.
2
Test Planning
in this phase, the test strategy is defined.
Objective & the scope of the project is determined.
3 Test Case Development
6
Test Cycle Closure
Test Closure is a document that provides a summary
of all the tests covered during the software development lifecycle.

8. What to learn for QA Manual &
Automation
Software Testing Fundamentals
Software Testing types, Software Testing Terminology , Advance QA Techniques .
Test Case Design
Creating effective Test Scenario , Test cases for manual and automated testing.
Automation Frameworks
Learning various automation tools and frameworks like selenium.

9. Type of Software Testing
Functional Testing
Incremental
Testing
Non-Incremental
Testing
Load Testing
Stress Testing
Volume Testing
Non- Functional
Testing
Unit Testing
Integration
Testing
System
Testing
Performance
Testing
Usability
Testng
Compatibility
Testing

10. Type of Software Testing
1. Functional Testing
 Unit Testing
- Unit testing conducts on single program or single module , small
components or program test by developer.
 integration Testing
- Integration testing performed between 2 or more modules.
- integration testing focuses on checking data communication between multiple
modules.
 Types of integration testing
1) incremental integration testing
2) Non- Incremental integration testing
(1) incremental integration testing
incrementally adding the modules and testing the data flow between the
modules
(2) Non- Incremental integration testing
Adding all the modules in a single shot and test

11. Type of Software Testing
 System Testing
System testing is type of Testing that Can be refer to Testing overall
functionality of the application with respective client req , this testing is
conducted by the testing team. System testing include:-
 User Interface Testing(GUI)
A GUI Testing is includes the all the elements such as
menus,checkbox,buttons,colors, fonts,sizes,icons,content,and images etc.
 Functional Testing
Functional testing talks about how your Feature / Module should work ?
 Object Properties Testing = verifying the elements properties
For example the radio button focus at only one field. (Like male or
female)
 Error Handling On UI = Verifying the errors on the UI.
 Calculation and Data Manipulations Testing.
 Links Existence & Links Execution - links were are the place - its
working Fine or not - click by link its go to the related page or not.

12. Type of Software Testing
2. Non Functional Testing
 Performance Testing (Performance Testing includes)
 Load Testing - Increasing the load on the application slowly/ then checking the speed of the
app.
- accessing lot of user application and check how the speed of app its under the load testing.
 Stress Testing - Suddenly we increase or decrease the load and then check the application
speed.
 Volume Testing - Size of app - how much the data should able to stored the application.
 Usability Testing
During this testing validates applications provide context sensitive help or not to the user.
• Usability Testing also known as User Experience (UX) Testing,
 Compatibility Testing
Compatibility Testing is a type of Software testing to check whether your software is capable of
running on different hardware, operating systems, applications, network environments or Mobile
devices.

13. Software Testing Terminology
 Regression Testing
 Testing Conducts on modified builds to make sure there will not be any impact on
existing functionality because of changes like adding. Deleting , modifying features.
 Re-testing Testing
 Whenever the developer fixes a bug tester will test the fixed bug is called re-
testing. Tester close the bug if it worked otherwise re-open and send to developer.
 Smoke Testing
 Smoke test is done to make sure the build we received from the development team is
testable/stable or not.
 Smoke testing is performed by both Developer and QA.
 For Example , test includes the build properly install or not and basics navigation or
feature are the run as proper or not.

14. Software Testing Terminology
 Sanity Testing
 Sanity test is done during the release phase to check for main functionalities of the application
Without going deeper.
 Sanity testing is performed by testers alone.
 It is done on stable builds
 It is planned when there is not enough time to do in depth testing.
 Exploratory Testing
 We have to explore the application, understand completely and test it.
 Understand the application , identify all possible scenarios , document it then use it for testing
 we do exploratory testing when there is no requirements are Defined.
 Ad HOC Testing
 Testing applications randomly without any test cases or any business requirement document.
 ADHOC testing in an informal testing type with an aim to break the system.

15. Advance QA Techniques
1
2
3
4
Equivalence Class Partition(ECP)
Boundary Value Analysis (BVA)
State Transition
Error Guessing

16. Advance QA Techniques
1. Equivalence Class Partition(ECP)
- Partition data into various classes and we can select data according to class the test.
- It reduces the number Of test cases and saves time for testing.
- For Example , We Have The Text Box Its Allow Number From 1 - 50 so ,
in ECP we partition the data inputs in various classes.
For Example, - 0 to 10 , 10 to 20 , 20 to 30 , 30 to 40 , 40 to 50 , -1 to -5 , 51 to 55
etc. and we test the first invalid or valid inputs.
A Text Box *Accept value only 1 to 50 Digits
Invalid Valid Invalid
-1 to -5 1 to 50 51 to 55

17. Advance QA Techniques
2. Boundary Value Analysis (BVA)
- BVA technique used to check Boundaries for the inputs.
- In this use the min value & max Vale in Below Format.
(Min Value -1) (Min , Min+1 , Max , Max-1 ) (Max + 1)
- For Example A Text box name of age (Age accepts value 18 to 56)
Age *Accept value only 18 to 56 Digits
Invalid Test Cases Valid Test Cases Invalid Test Cases
(Min value -1 )
17
(Min , Min +1 , Max , - Max 1)
18 , 19 , 56 , 55
(Max Value +1 )
57

18. Advance QA Techniques
3. State Transition
- The State Transition is Usen when user has multiple conditions for test case.
- Using state transition testing, we pick test cases from an application where we need to test different system transitions.
- The tester can perform this action by entering various input conditions in a sequence.
- State transition testing helps to analyze behavior of an application for different input conditions.
Example
Entering the correct password in the first attempt or second attempt or third attempt, user will be redirected to the home
page (i.e., State – S4).
Entering incorrect correct password in the first attempt, a message will be displayed as try again and user will be
redirected to state S2 for the second attempt.
Entering incorrect correct password in the second attempt, a message will be displayed as try again and the user will be
redirected to state S3 for the third attempt.
Entering incorrect correct password in the third attempt, user will be redirected to state S5 and a message will be
displayed as “Account locked. Consult Administrator”.

19. Advance QA Techniques
3. State Transition Example

20. Advance QA Techniques
4. Error Guessing
- Error Guessing is one of the testing
technique used to find bugs in a software application
based on tester’s Experience.
- In error guessing we don't follow any specific rules.
- it depends on tester analytical skills and experience.

21. QA Testing Documents
Test Plan
- Test Plan is a Document that describes the test scope , Test Strategy , Objectives , Schedule , Deliverables
and resources required to Perform Testing for a software product.
- Test Plan Template Contents
 Project Overview
 Scope
- inclusions
- Test Environments
- Exclusions
 Test Strategy
 Defect Reporting Procedure
 Roles / Responsibilities
 Test Schedule
 Test Deliverables
 Pricing
 Tools For used in
Software testing
 Risk
 Approvals

22. QA Testing Documents
Test Scenario
A test scenario is a One liner statement that describes the functionality of a software application to be tested.
(It Clarifies what to test ?).
•It is also called a Test Condition or Test Possibility.
•Test Scenario Covers the entire functionality of the software application.
 Test Case Contents -
- Test Scenario ID
- Test Scenario Description
- Priority
Example
# Verify that User can Signup Easily or not.
# Verify that User can Login With Valid or Invalid Credentials or not.
# Verify User can Login with Social Logins

23. QA Testing Documents
Test Case
A test case is a set of steps and conditions that are used to verify the functionality and quality of a software application.
•Test cases are derived from the test scenario.
https://prnt.sc/BY54IZRiTY0G

24. QA Testing Documents
How to Write a Effective Test Case
1.Define the area you want to cover from the test scenario.
2.Ensure the test case is easy for testers to understand and execute.
3.Understand and apply relevant test designs.
4.Use a unique test case ID.
5.Include a clear description in each test.
6.Create Test Case with End User in Mind
7. Avoid test case repetition.

25. QA Testing Documents
Bug Report
A software bug report contains specific information about what is wrong and what needs to be fixed in software or on
a website.
* Defects / BUG Report Contains
- Defect ID
- Defect Description
- Steps to Reproduce
- Attachments
- Severity
- Priority

26. How to Represent A Bug In tool

27. Bug / Defect Life cycle
Tools For (Manual)
Test Management

28. What is Automation Testing
 Automation Testing is a software testing technique that
performs using special automated testing software tools
to execute a test case suite.
 Test Automation in software testing does not require
Human intervention. You can run automated test
unattended (overnight).
 Test Automation increases the speed of test execution.
 Automation helps increase Test Coverage.

29. How to be an Automation QA Engineer
 You Need a Technical Skills.
 Need Programming languages knowledge like (Java, Python , C# ,
JavaScript , Ruby)
 You Should Knowledge of the Framework Tools Like Selenium , Appium
 Knowledge About API.
How does automated testing work?
1. Choose a testing tool that suits the type and platform of the software testing.
2. Define how much automation is needed for the testing process.
3. Plan the automation strategy and develop test scripts accordingly.
4. Run the test scripts and collect data and reports from the testing tool.
5. Maintain and update the test scripts as the software changes.
Tool For Automation

30. Difference Between Manual and Automation Testing
 In manual testing, the test cases are executed by the
human tester.
 Manual testing is time-consuming.
 There is no need for programming knowledge in
manual testing.
 Exploratory testing is possible in manual testing.
 In manual testing, investment is required for human
resources.
 Manual test Case are cannot be batched.
 Manual Testing has a higher risk of missing out the
pre-decided test deadline.
 In automated testing, the test cases are executed by
the software tools.
 Automation testing is faster than manual testing.
 Programming Knowledge is Required in automation
testing
 Exploratory testing is not possible in automation.
 In automated testing, investment is required for tools
and automated engineers.
 You can Batch multiple Test Cases.
 Automated Tests have zero risks of missing out a pre-
decided test.
Manual Automation

31. QA Job Part
Understanding the
requirements
Creation Required test
scenarios
Designing Test cases
Setting up Test Environment
Execute test cases
Log Test results (Pass or Fail)
Defect reporting and tracking
in Tool
Retest fixed defects
Perform various types of
Testing
Reports to Test lead about the
Status
Provides Confirmation Project
Is ready For Production or Not

32. Learning basic skills for Manual And Automation Engineer
 Task Management
 Verbal and written Communication
 Analytical Skill
 Critical Thinking & Problem-solving Skills
 Thinking as end user
 Programming Language knowledge
 Test Scrip Creation
 Manging Testing tools

33. Build Career in QA
 QA Engineer
 Sr. QA Engineer
 QA Team Leader
 QA Manager
 QA Director

34. Types Of Test Engineers
 Web testing
 Application Testing
 Data Base Testing
 Desktop Application Testing
 Game Testing

35. Demo Task
Create Test Scenarios
Execute Test Script
Create Test Scripts
Report Defect
Application Demo Flow

36. Demo Task
Create Test Scenarios
Execute Test Script
Create Test Scripts
Report Defect

37. Demo Task
Create Test Scenarios
Execute Test Script
Create Test Scripts
Report Defect

38. Execute Test Script

39. Execute Test Script

41. Practical Task
Test Scenario Table
Login Screen 4.0 4.1 Write Test case for Login Screen User Interface
4.2 Write case for Login Button Disable when Mobile No. not entered
4.3Write test case for Application able to login with Registered Mobile No.
Prerequisites are the Latest applications installed in the Device.
Test Scenario: Login Screen 4.0
Test Scenario 4.1 Write Test case for Login Screen User Interface
Test Script 04: For Check login screen User interface
No Step Expected Result Actual Result
1
Write Test Script/Case in below Format

42. Links of for learning QA Software Testing
Web Links
 https://www.guru99.com/software-testing.html
 https://www.javatpoint.com/quality-assurance
YouTube Course (Channel Name – The Testing Academy )
Manual
 https://www.youtube.com/watch?v=P31bOYX1lZE&list=PLwbMf8x0S9vBcE3i5qtf0BrqXS9OZ1LXR
Automation
 https://www.youtube.com/watch?v=Uk8iDmacN0U&list=PL8VbCbavWfeG_QP9yIylsXOCb8CJunKU_

43. Follow Us on in.linkedin.com/company/whitelabelfox
@whitelabelfox @hr_whitelabelfox