Batch 189

Agenda of the Session:

-Indian Bank wants to build a Web Application for core Banking services or Net Banking

services

- TCS started working on this project-Core Banking Services

Project Name: CBS

Client Name: Indian Bank

Type of Application: Web Application

Requirements-BA1-Suresh, BA2-Ramesh

Design -Technical Architect- Sathish

Project Manager- Mahesh

As per the Architecture of this project,

Data Base: MYSQL

UI/Front end: React JS (HTML,CSS, Bootsrap,JQUERY)

Middlewere/Logic: Node JS

Developers :

DB Developer: Sravanthi-MYSQL

UI Developer: Sindhu, Lavanya, Srinu

Node JS Developer: Syed, David

Testers: Manual+Automation

Shabana, Jyoti

Admin-Devops+AWS

Stu

Developers started creating Source code of the application

UI Dev-UI Code

App Dev-App Code

DB-DB Code

1. Develop Component or program or Unit

2. Each component must be reviewed or Code review

3. Code Complilation

4. Unit Level testing using White Box methodlogy

Unit testing is examples:

Unit testing done by UI Dev 1 to validate Login working or not

Unit testing done by UI Dev 2 to validate Pay User working or not

Unit testing done by UI Dev 3 to validate QR code working not

Unit testing done by App developer1 to validate Login logic working or not

Unit testing is done by App developer2 to validate Payment logic

working or not

Unit testing is done by DB Developer 1 to validate customer table

created correctly

Unit testing is done by DB Developer 1 to validate account data created correctly

Unit testing is done by DB Developer 1 to validate Payments data

What is Unit testing?

Ans:

1. What? Once Code component is created by each developer, Each component must be tested

to check whether each component output is correct or not

Checking each component of the code working or not

2. Who? Developers are the right people to perform Unit testing or SDET

3. Which Methdology? White box methdology is required to perform Unit Testing-Code access must be given

4. When? Once code review is done, then only Developers perform Unit testing

5. Unit test is code written by dev to tets code -->

Unit test can be done using two approaches

5.1 Manual Unit tetsing

5.2 Automated Unit Testing

6. As part of Unit Testing -

Payment Functionality working or not

What are the differences between Unit testing and Integration testing?

Diff 1:

Purpose of Testing or Scope of Testing or Objective of Testing:

Unit testing purpose is each component working or not where as

Component Integration testing(CIT) purpose is check flow across UI-DB or DB-UI or

UI-Logic-DB this flow working as desired or not

Diff 2: Wheevener Component is developed, Code review completed then we can start

Unit Testing, where as if multiple components are Integrated the to check how

flow working developers will do Integration testing

Diff 3: Unit tetsing is done at Developer workstation where as CIT-Component Integration

testing is done at Dev server

Enviornment is different

SYSTEM TESTING:

Once AUT -Application Under test is deployed in Testing server,

Test Engineers responsible to perform two types of testing

1. Functional and 2. Non Functional testing

As a Functional tester my job is once code deployed in testing server, I will do Functional

testing to Web Application..As part of Functional testing, I will perform field display

test, Business Logic test, End to End flow Test

Functional

-Field Display

-Business Logic

-End to Emd flow

Non Functional

-Performance testing

-Security testing

-Compatability testing

-Usability testing

-Localization testing

This Functional testing can be perfomed using two approaches/Methods

1.Manual Functional testing

2. Automated Functional testing

Manual Web Application Functional testing -Testing server/System level

Automated Web Application Functional- Testing SYSTEM TESTING

My role is System test Engineer,

My role is Functional test Engineer

My role is Manual testing

My role is Web App testing

My role is Black Box testing

-----My role is Manual testing, Web App, Functional, System Test Engineer

using Black box Methodology

---My role is Automation testing using Selenium, Web App, Functional, System Test Engineer

using Black box Methodology

----My role is Manual+Automated testing of Web App/Mobile Apps/DB/API

for Functional testing which

is deployed in System Testing server using Black box Methodology

Levels of Testing:

Unit Level

Integration Level

System Level

System Integration Level

User Acceptance Level

Types of Testing:

Functional

Non-Functional

Test Approaches/Methods:

Manual

Automation

Testing Methodologies:

White BOx

Black Box

Grey Box

----------------------------------------------------------

Once Application is deployed in testing Server, Testing team can perform two types of

Testing

1. Functional Testing

2. Non-Functional Testing

What is Functional testing?

How to perform Functional testing?

What is Non Functionl testing?

How to perform Non-Functional testing?

What are the Functionalities of Human Body?

- Eyes

-Skin

-Nose

-Brain

-Heart

-Lungs

- Head

Answe: Wrong

Components of Human Body

Organs of Human Body

Thinking

Reading

Writing

Drinking

Smelling

Speaking

Walking

Running

Eating

Swimming

lifting

Seeing

An Action or Task or Actitivity which we can perform using Few components

What are the Functionalities of Web Application-Core Banking

Functionalities of Web Application are:

1. Creating new customers

2. Updating customer details

3. Deleting customers

1. Creating Account

2. Updating Account

3. Deleting Account

1. Creating Payment

2. Transferring amount via payment

3. Updating payment details

4. Stop Payment

5. View payment

6.Adding Intreset

7. Deleting Interest

8. View Interste

Functional Requirememts are given to both Developers and Test Engineers

Checking each functionality working as per conditions/rules/Logic mentioned as per

Functional requirement document (FRS)

Expected Functionality: Requiremen document: FRS Document

Adding an amount driver tip will add the amount to the total amount

Adding a percent driver tip will calculate the percent value based on the

sub total and add it to the total amount

Other driver tip max value is 99 €

Driver tip is not displayed for pickup orders.

If driver tip is selected and user changes to

pickup, the driver tip value should disappear

Example 1: Checking Driver tip Functionality working as per above logic

Voucher can have a minimum value to be used.

Voucher can also be set up to be used only for newly registered users

There are following types of vouchers

1. Amount off voucher : code: AMOUNT_FOR_TA

10 euro minimum value for the order

It removes 5 euro from the total value

2. Percentage of the order: code: PERCENT_FOR_TA

10 euro minimum value for the order

It removes 5% from the total value

3. Delivery fee free: code DELIVERYF_FOR_TA

euro minimum value for the order

It removes the complete delivery fee from the total valu

What is Functional testing?

Checking AUT/SUT is working as per the logic/rule/condition mentioned in FRS Document

How Functional testing is perfomed?

Functional testing to Web Application: Checklist 1

Functional testing to Mobile Apps: Checklist 2

Functional testing to API/Webservoce: Checklist 3

Functional testing to DB/Datawarehouse: Checklist 4

How to do Functional testing to Web Application????

1. Field Display:

Whenever a new form/Field added to Web Application,

check for the displayof the field

1. Is field Name correctly created as Per UI Design

2. Is field Type correcyly created as per UI Design

3. Is field Color correctly created as per UI Design

2. Business Logic/Condition/Rule/Transaction:

Give inputs application as per logic check are we getting correct output?

2.2.1 Business Logic Positive Test

test by giving valid inputs

Test with AMOUNT_FOR_TA code

Expected Result: Amount-5 euros

Test with PERCENT_FOR_TA

Expected Result: Total Value-It removes 5% from the total value

test by giving Invalid inputs Business Logic negative test

2.2.2 Business Logic Negative Test

Test with AMOUNT_FOR_TARAMANAAjcgjszdjsz code

Expected Result: Error message -Correct

Test with AMOUNT_FOR_TA

Purchase amount=9Euro

Expected result: Code is not applicable

3. End to End flow:

Testing journy of a customer with your application

Testing flow of the application from beginging to Ending

Example 1: Netbanking application

End to End flow Testing1:Happy Path: Shortest End to End flow

End to End flow Non Happy Path/Un Happy Path: Longest Flow

Change Pwd + Logout

End to End flow Testing:

Happy Path Flow: Shortest Path with Mandatory fields

Non Happy Path Flow : Longest Path with Mandatory and Optional fields

What is difference between Positive Test and Negative Test?

Test with expected Input to see how your application processing is called

Positive Test Where as Test with Invalid/unexpected/Extremly different inputs to see

your application capable of recongizing invalid inputs and giving correct error message

as output

3. End to End flow

Functional testing to Web Application

1. Display

2. Logic-->Positive/Negatuve

3. Flow -->Shortest/Longest

As a Functional tester my job is testing web Application field Display,

Business Logic positive, Business Logic negative, End to End flow happy path,

End to End flow Non happy Path once application depoyed in Testing Server using

either Manual approach or Automation

Developers

Unit Level testing

INT Level testing

Testers

System Level testing

-Functional -Display/Logic/Flow

-Non Functional

SIT Level testing

Customer

UAT Level testing

-----------------------------------------------------------------------------

Once code is deployed in Testing Server-Build Version 1-System Testing Starts

How System Level Testing Happens???

1. Any one Test Engineer will perform Smoke Testing to

check basic functionality working

Smoke testing is a type of Testing which verifies the product is qualified enough to

robust testing or detailed testing

Ex: Electronics circuit

If Smoke is coming of Electronics circuit this indicates product is not qualified

to continue testing

In electronics and electrical engineering,

the term smoke test or power on test is used to refer to the

first time a circuit under development is attached to power, which will sometimes

produce actual smoke if a design or wiring mistake has been made.

The expression probably was first used in plumbing in referring to tests for

the detection of cracks, leaks or breaks in closed systems of pipes

Checking First Version of the Build to know

"Is this Qualified enough to continue Robust or Detailed Testing"

https://demo.cyclos1.org/ui/login

Critical Issue or

ShowStopper Defect

---- Whenever first version of the Build is deployed or Installed -------

As a test Engineer we perform Smoke testing

How we perform Smoke Testing:

1. Open Landing page

--- If we are getting Blank Page or Technical Error -Page cannot be displayed

Smoke testing failed -Unable to start testing

2. Check Basic flow -Test Application with Simple Happy Path -End to End flow

Pay User

Sleect One customer

Select IMPS Option

Transfer

Transaction Succesful

3. Smoke Testing results are pass -Send results to developer for confirmation

and Ask your team continue detailed Functional Testing

Detailed Functional Testing:

Field Display-100 Tests

Business Logic Positive-250

Business Logic Negative-100

End to End flow Happy Path-20

End to End flow Non Happy Path-35

As a Functional tester of Web Application, As part of System testing my responsibility

is performing below tests:

1. Smoke Test

2. Field display

3. Business Logic Positive

4. Business Logiv Negative

5. End to End flow Happy Path

6. End to End flow Non happy Path

7. Re-Testing of the defects

8. Automated -Sanity-Regression testing

If Any above test fails, what testers wil do???

Ans: Report defect using defect Tracking tool-JIRA

Testet Submit defect to developer

1. Email-1990s

2. Excl-Defect Tracking Template

3. Defect Tracking tools-Quality Center-2006

4. Project Management Tools-JIRA/Azure Devops/Rally

JIRA-->ATLASSIAN

Azure Devops-->Microsoft

Once Tester report defect to Developer, Then Developer fix the defect in dev Machine,

They again test in Devserver, if working in Dev server

then they deploy latest version of the build in testing server

Total How many test

3+3+3

Smoke Test =1

Field Display=3

BL=3

E2E=3

Total Tests=10

How Many test Pass=7

How Many Failed =3

Defect 001,002,003

How Many retest-3

Testing Summary=100%Pass

B1.0:

How Many tests we have executed=7

How many Pass=5

How many fail=2

B2.0:

New test cases=3

Retest=2

Tests executed=5

Pass=4

Fail=1

B3.0

New Tests executed= 0

Retest=1

Test executed=1

Pass=1

Fail=0

Which build-Version is going live?

Ans: B3

Version 2 is modified version of Version 1

Version 3 is modified version of Version 2

B1+ Modified-->B2

B2+ Modified-->B3

B1: 7/5-5 pass

B2: 5/4 -5 retest/new

B3: 1

Who will give gurantee 5 which are passed in version 1 still work in Version 3?

Who will give gurantee 4 which are passed in version 2 still wotk version 3?

V1-10 Tests

10 Pass

V1-->Live

V1-10 Tests- 5 Pass/5 Fail

V2- 5 fail-retest-5 fail pass

Any Changes

- Bug Fix

- Env changes

- Enhancements+ Extra Features+ New Features

B1+B2+B3

Any Changes or Modification -

-Changes must work correctly

-Changes must not introduce side affects

After changes previosuly working tests may work/May not work

We recommend Testing team to retest previosuly working test cases again before

we release application to live

Regression Testing is a Kind of Selective/Full retesting

Retest focus on re-executing previously failed case

Regression foucs on re-executing previously working case

B3-->1+9

Total Tests:10

How many tests are elgible for Regression Testing: 9+1

Time to executed 5 tests as part of Regression testing: 5

% of Regression test coverage:50%

T1,T2,T3,T4,T5,T6,T7,T8,T9,T10

On what basic we decide Regression test suite? 5

Why 50%-70%

I want more regression testing in less time

Hire more testers -10r

Ask more time

Automation testing

Unit=0

CIT=0

SYS=90%

SIT=8%

UAT=2%

Agenda of the Session:

1. Continue understanding of System Testing

2. Understanding of SIT Testing

3. Understanding of UAT Testing

What Happens in System Testing:

1. Smoke Test

2. Field display

3. Business Logic Positive

4. Business Logiv Negative

5. End to End flow Happy Path

6. End to End flow Non happy Path

7. Re-Testing of the defects

8. Automated -Sanity-Regression testing

During Bug Traige Meeting-Every day

1. Is this Defect Valid defect or Invalid?

2. Are we going to fix in current release?Postpone to next release? Bandwidth -

Deferred defects

3. Who is the right developer to fix?

PM,Dev team,Testing Team, BA

Tester identified defect during System testing :

Understanding different scenarios of retesting:

1. Tester reported defect in JIRA Tool and assign to developer

2. This defect is valid but devlopers decided to fix next month -Deferred Defect

3. This defect is Invalid ,Developers reject-Tester retest , if really Invalid

-Close the defect

4. Defect is Valid , Dev fixed it, tester retest, if working tester close defect

5. Defect is Valid, Dev fixed it, tester retest, its not working again,

tester reopen the defect, Again dev fix, Again tester retest, if working-close it

R1,R2,R3-->

-------------------------------------------------------------------------------------------------------------------------------

Till now what we discussed?

1. Unit Testing

2. Integration Testing

3. System testing-Non Functional

Agenda of the discussion:

SIT Testing

UAT Testing

SIT Testing: System Integration Testing

Redbus -->To Book Ticket

1. Search Ticket

2. Select Ticket

3. Login

4. Payment-->PhonePay/Gpay/Debit/Netbaking

5. Order confirmation Message/Mail -

Application 1: Ticket Selection-->Redbus developer

Application 2: Google Maps/Apple Map-->Thirdparty Software

Application 3: Payments -Phone Pay/Gpay........

Application 4: SMS?Whatspaa/Email

Redbus

Every Application connected to multiple other applications

Unit testig -Application 1

CIT testing-Application 1

System testing-Application 1

Application 1+ Application 2-->SIT Test 1

SIT Test 1+ Application 3-->SIT Test 2

SIT Test 2+Application 4-->SIT Test 3

What is SIT testing?

1. SIT testing is checking how our application is working inconjunction

with other applications

2. SIT testing is perfomedin SIT Testing Server

3. SIT testing is done by tes engineers using Black Box to check Both Functional and

Non Functional

4. SIT testing objective is checking how our application is working outside where

System testing objective is checking how our application is working inside

5. SIT testing need not to be detailed test-SIT is sanity -Selective Testing points

6. Once each application qualified in System level then only SIT testing is performed

SIT testing is checking how your application working inconjunction with other applications

SIT Sanity Functional checks

SIT Non Functional check

SIT retesting

SIT regression

UAT Testing: User Acceptance Testing

-UAT Testing: User Acceptance Testing

- Testing is done by end user/End customer /Business User/Key User with support of

Testing team

-UAT testing purpose checking software working as per Acceptance criteria

defined by customer

- If Application qualifies in UAT testing, then customer decide as fit for deployment

-Go Live

- In UAT tetsing, customer use live data/Real data

UAT Round 1-->Alpha

UAT Round 2-->Beta 1.0

UAT Round 3-->Beta 2.0

-In UAT testing enviornment close to production/Mirror immage of production

UAT testing is done by end users with real data-Day to day scenario

UAT Testing- Sanity testing is Enough

1. End users

2. Real data

3. Real scenarios

3. Real Server

UAT Testing

Level 1-Alpha

Level 2-Beta

-----------------------------------------------

1. Testing Technqiues-->Static testing/Dynamic Testing

2. Testing Methdologies-->Whitebox/Black

3. Testing Levels-->Unit/INT/SYS/SIT/UAT

4. Testing Types-Functional/Non Functional

5. Testing Methods

Regression Testing vs retesting

Smoke Tetsing vs Sanity

Positive testing vs negative

Formal testing vs Adhoc Vs exploratort

Manual vs Automation

Alpha Testing vs Beta testing

6. Testing princples

Pending Topics : 1hr

1. Non Functional

2. Testing princples

3. Formal vs Adhoc vs Exploratory

4. Manual vs Automation

5. Aplha vs Beta

Interview Questions list from chapter 1:

Saturday: Interview

Tuesday: STLC -Manual testing Chapter 2

Search This Blog

189 testing

Batch 189

Comments

Post a Comment

Popular posts from this blog

smoke and Sanity Testing

Case