FUSIONX QA

SPRINT
 W H AT I S Q U A L I T Y A S S U R A N C E ( Q A )

Quality assurance (QA) is any systematic process of determining whether a

product or service meets specified requirements. QA establishes and maintains set

requirements for developing or manufacturing reliable products.

T Y P E S O F S O F T WA R E T E S T I N G
 MANUAL TESTING
 Manual Testing is a type of software testing in which test cases are
executed manually by a tester without using any automated tools. The
purpose of Manual Testing is to identify the bugs, issues, and defects in
the software application. Manual software testing is the most primitive
technique of all testing types and it helps to find critical bugs in the
software application.
Manual Software Testing - Process Lifecycle
 TOOLS OF QA
 Recently we are used as manual testing tool in QA
environment.

 Jira helps teams plan, assign, track, report, and manage work and
brings teams together for everything from agile software
development and customer support to start-ups and enterprises.
 We are used as REST API Documentation tool in QA
environment.

 Swagger UI allows anyone — be it your development team or your end

consumers — to visualize and interact with the API's resources
without having any of the implementation logic in place.
 URS (USER REQUIREMENTS
SPECIFICATIONS)

 What is user requirement specification?

 What is a user requirements specification (URS)? In software
engineering or systems design, a URS is a planning document
that specifies what the software or system needs to do. It is
written from the point of view of the end user and does not need
to be technical or complicated.
Sample of the URS
 MANUAL TEST CASE WRITING

 What is a manual test case?

 Manual testing is a software testing process in which test cases are
executed manually without using any automated tool. All test cases
executed by the tester manually according to the end user's perspective. It
ensures whether the application is working, as mentioned in the requirement
document or not.
 Initially we used MS Excel and presently using Jira to test case writing
in manual testing.
Testcase Document - Business Type
Jira Testcase task interface
Test (Testcase)
Test details
Test Runs
Issue Types
CREATING ISSUE ON JIRA BOARD
 API TESTING

 API testing is a type of software testing that analyzes an application program

interface (API) to verify it fulfills its expected functionality, security,

performance and reliability. The tests are performed either directly on the API or

as part of integration testing.

We are used as an API / API development tool in QA environment.

Postman is an API(application programming interface) development tool which

helps to build, test and modify APIs.
Postman Interface
Bank Transaction Code Controller Collection 
HTTP Request Headers
POST HTTP Request
GET HTTP Request
PUT HTTP Request
Before Try it out
After Try it out
POST HTTP Request Curl and URL
Main HTTP Request Methods
 HTTP STATUS CODES

Commonly we are seen these HTTP Status Codes in QA environment.

200 - OK
201 - Created
422 - Unprocessable Entity
500 - Internal Server Error
417 - Expectation Failed
204 - No Content
401 - Unauthorized
404 - Not Found
400 - Bad Request
422 - Unprocessable Entity
201 - Created
200 - OK
417 - Expectation Failed
500 - Internal Server Error
204 - No Content
401 - Unauthorized
404 - Not Found
400 - Bad Request
 COB (CUSTOMER ONBOARDING)

 COB is one of Core Banking Solution module in QA Fusionx.biz web.

 Customer onboarding is the process that new users go through to get

set up and start using your product.
THANK YOU!