TESTING

Presented By :-
Akhilesh Singh
Amit Sharma
Arpan Maheshwari
Arpita Datar
Kavitha Venkatesh
Shitij Anand
Swati Saini

|


 

  AT IS TESTING?
u Testing is an investigation conducted to provide
stakeholders with information about the quality of the
product or service under test.

u Software testing also provides an objective,

independent view of the software to allow the
business to appreciate and understand the risks at
implementation of the software.

u Software testing can also be stated as the process of

validating and verifying that a software
program/application/product.

|


 
 -BJECTIVES - TESTING

u Executing a program with the intent of finding an

„
.

u To check if the application meets the requirements

and be executed successfully in the Intended
environment.

u To check if the application is ´ it for purposeµ.

u To check if the application does what it is expected to

do

|


 
Î
 BLACK B-
TESTING

-BJECTIVE:

u


 

u 

u 

 

|


 

  AT AND 
T E NAME?

uhat is black box testing?


 



 

uhy named as black box testing?
*
 

|


 

  - , EN AND 
?
u ho does black box testing?





u hen you do?

-   
!

u hy not by developers?

¢ 

 
 
"# !
$ 

 %
|


 
&
 B-NDAR
VALE ANAL
SIS
If software can operate on the edge of its
capabilities, it will certainly operate well under
normal conditions.

|


 
w
 ERR-R GESSING
Tester guesses from his /her experience on the error-
prone area and concentrates around that area.

Example : hen the bike stops, first thing you do is ²

check the petrol.

ou probably wont
- go to mechanic or
- read the manual or
- check the spark plug

ou know from your experience or
usage that petrol could be over.

|


 
Õ
  ITE B-
TESTING

|


 
Ú
  AT IS IT ?

u Testing the internal structure of the software

nderstand the code and the code will set you free!

u hite-box testing is testing that takes into account

the internal mechanism of a system or component

u It·s also known as Structural testing, clear box

testing and glass box testing

|


 
'
 TEC NIQES

uStatement coverage

uLoop testing

uPath testing

uBranch testing

|


 

 AT-MATED TESTING

Coding Process with Automated nit Tests

"


# "
 

 
 
# "

(
#)"



"

(
#)
 " 

|


 
*
 MANAL TESTING
Coding Process with Manual Tests
 
+
  "


,  "

-"


" .

/0


01 
2! 0
¢
!


"0- 
 
(
0
 
! 

|


 
Î
 AT-MATED TEST VS MANAL TEST

u Manual Testing is not reusable

  
"
"
-

3



u Automated Tests are completely reusable

(34-,56-
 
(
2!0
 "" ,



7
 
-  "
"

 


 
 



 " 48 

|


 

 AT-MATED TEST VS MANAL TEST (C-NTD«)

u Manual Testing ends up being an Integration Test

(

"

! 


("  "
  
 

 

! 
( 
9 " 

 
"





u Automated Tests can have varying scopes

-

- 
:" .0
"0

"

|


 

 ASAP MET -D-L-G

Accelerated SAP Methodology

u@he ASAP Methodology provides roadmap for implementing
and continuously optimizing your SAP System.
uIt divides the implementation process into five phases and
offers detailed Project Plans to assist.
u Accelerated SAP contains a multitude of tools, accelerators
and useful information to assist all team members in
implementing R/3.

|


 
PROJEC@ PREPARA@ION
—-/21(5—
8 


(34/1315(-521—*
% 
  ""
%
*%1
  8 
7

!

""

 

(34/1315(-521;+15 1
 8 
  

13

"<8 
"< 

"

2(—5-$$
 


!
 "
 
|


 
 BSINESS BLEPRINT
u The purpose of this phase is to achieve common
understanding of how the company intends to run SAP
to support their business.

u To refine original project goals and objectives and

revise the overall project schedule in this phase.

u The result is the Business Blueprint, a detailed

documentation of the results gathered during
requirements workshops.

|


 
O SINESS O
EPRIN@
2 -41- +315
  " 

 %

2(2
%+
  " 

"%
*%
 2(2 "


%

-1
%(  "
  

24

—45/*2(2
% —42(2 
-1




%
*%—4 "
 
 %
|


 
 REALIZATI-N
u The purpose of this phase is to implement all the
business process requirements based on the Business
Blueprint.

u The System configuration methodology is provided in

two work packages:
1.Baseline(major scope)&
2. inal Configuration(remaining scope)

u In this phase documentation is created for the

configuration implemented and it has to be taken sign
off from client.

|


 
 INAL PREAPARATI-N

u The purpose of this phase is to complete final preparation which

includes the following:
1.nit Testing : Testing within each module.
2.Integration Testing : Combined testing of all the module which is
implemented.
3.ser training and testing : End user of each module will be
provided training by corresponding
module consultant.
4.Cut -ver Strategy : Before Go Live Process cut over period for the
business process is carried. During this
process the master data & Transaction data
from legacy system will be migrated to SAP
system.

|


 
*
 G- LIVE AND
PER CARE

u The purpose of this phase is to move from a project -

oriented, pre-production environment to live
production environment.

u The most important element include setting up

production support, monitoring system transactions
and optimizing overall system performance.

|


 
 T
PES - TESTING

u nit Testing
u System Testing
u Integration Testing
u Regression Testing
u ser Acceptance Testing
u Performance Testing

|


 
*Î
 NIT TESTING

Tests the smallest individually executable code units.

sually done by programmers. Test cases might be
selected based on code, specification, intuition, etc.

Tools:
u Test driver/harness
u Code coverage analyzer
u Automatic test case generator

|


 
*
 INTEGRATI-N TESTING
Tests interactions between two or more units or
components. sually done by programmers.
Emphasizes interfaces.

Issues:
uIn what order are units combined?
u ow do you assure the compatibility and
correctness of externally-supplied
components?

|


 
*
 S
STEM TESTING

u Purpose
Test the entire system as a whole

u Assumptions
Completed
 nit Testing

 Integration Testing

|


 
*&
 REGRESSI-N TESTING
ï



USelective retesting to detect faults

introduced
during modification of a system or
system component, to verify that
modifications have not caused
unintended adverse effects, or to verify
that a modified system or system
component still meets its specified
requirements.´
U...a testing process which is applied
after a program is modified.´

|


 
*w
 SER ACCEPTANCE TESTING

u Purpose
The purpose of user acceptance testing is to verify
system from user perspective

u Assumptions/Pre-Conditions
 Completed system and regression testing
 Test data
 inal versions of all documents ready
 -verview to the testing procedures
 Specific procedures

|


 
*Õ
 PER -RMANCE TESTING

u Purpose
The purpose is to verify the system meets the
performance requirements.

u Assumptions/Pre-Conditions
 System testing successful.
 Ensure no unexpected performance.
 Prior to Acceptance Testing.
 Tests should use business cases, including
normal, error and unlikely cases

|


 
*Ú
 Testing @ SAP Landscape

 or testing single component like SAP ECC 6.0««..

 SAP recommends 3 landscape
-Development
-Quality
-Production
 nit testing is executed in Development system
 System Testing, Integrated Testing is executed in the Quality
Assurance System
 Load Testing, AT is executed in the Pre Production System

|


 
Î'
Testing @ SAP system Landscape

|


 
Î
SAP Testing : Efficient Approach

|


 
Î*
 SAP S-LTI-N MANAGER(SolMan)

 SAP solution manager provide

-tools,
-services
-methods
-technical and applications related documents
 ull Control on entire IT infrastructure
 Support all phases of entire lifecycle of software solution
-Implementation
--peration
-Support

|


 
ÎÎ
 SAP QALIT
CENTER (QC) by P

u SAP Quality Center by P is web-based test management tool

u Easy interface to manage and organize various testing activities.
u QC supports
-Manual Testing
-Automation
-Business Process Testing
u SAP Quality Center by P provide visibility and traceability
throughout the application lifecycle.
u P QC contribute around 60% of the market share in the Test
Management Tools.

|


 
Î
 SAP SolMan + SAP QC = Accelerated Testing

u SAP Quality center by P is a web-based test management tool

which gives a centralized control over the entire testing Project .
u Easy interface to manage and organize activities like
-Requirements coverage
-Test Case Management
-Test Execution Reporting
-Defect Management
-Test Automation
u Business process from Business Blueprint -> Requirements to the
SAP Quality center
u Requirements are further converted into Test Cases in the Test
Plan
u Test Cases are executed in the Test Lab
u Test results are analyzed in QC and updated back to SolMan.

|


 
Î
|


 
 Showcase : Business Scenario

 SAP ERP System ² Sales Process

Sales Process ; -rder ² Delivery ² To ² PGI ² Billing
e will explain complete sales process and various needs of
testing requirements by showcasing various tools available in the
Market.

 Create a Sales -rder transaction for customers with whom your

company has business relationships. ith respect to this order,
delivery and Billing Documents are generated.

 This business process will be showcased with Regression Testing

and Performance Testing.

|


 
Îw
 Business Scenario : Sales Process low

  ï  
        
 ï 


|


 
ÎÕ
 BSINESS SCENARI- : KE
TERMS

u Test Scenario
Test Scenario is the high level business process that
has to validated

u Test Case
Test Case is the sequence of steps to executed the
business flow

|


 
ÎÚ
Business Scenario : Process low ««««.01

|


 
'
Business Scenario : Process low «««.02

|


 

Business Scenario : Process low «««.03

|


 
*
Business Scenario : Process low «««.04

|


 
Î
Business Scenario : Process low «««.05

|


 

Business Scenario : Process low «««.06

|


 

Business Scenario : Process low «««.07

|


 
&
Business Scenario : Process low «««.08

|


 
w
Business Scenario : Process low «««.09

|


 
Õ
Business Scenario : Process low «««.10

|


 
Ú
 SALES PR-CESS: REGRESSI-N TESTING ««.11

Regression Testing
-partially retesting a modified program
-general assurance that no additional errors were
introduced in the process of fixing other
problem
-Repetitive process
-Automation

|


 
'
SALES PR-CESS: REGRESSI-N TESTING ««.12

|


 

SALES PR-CESS: REGRESSI-N TESTING ««.13

|


 
*
 Sales Process : Performance Testing «««..14

Performance Testing
-system performs under particular workload.
-validate and verify scalability, reliability and
resource usage
The different types of Performance testing :
-Load testing
-Stress testing
-Endurance Testing
-Spike Testing

|


 
Î
Sales Process : Performance Testing «««..15

|


 

Sales Process : Performance Testing «««..16

|


 

Sales Process :Reusable Business Components «..17

|


 
&
Sales Process : SAP TA- ««..18

SAP Test Acceleration and -ptimization

-Generate automatic tests during regression
testing of SAP solution, quickly.
-Creates component from the screens of a
transaction and parameterizes them.
-Supports maintenance of components

|


 
w
Sales Process : SAP TA- ««..19

|


 
Õ
Sales Process : SAP TA- ««..20

|


 
Ú
 Advantages

 The SAP Solution Manager and Quality Center Integration

-best of breed test tools
-Integrated test suite for all application
-speeds test preparation and execution
-provide single point of access to the entire software
landscape
-Structured Repository of test scripts with reusability
-End to end traceability
-improve Tester Productivity

 Comprehensive End to End Business Process Testing Solution that

-accelerates testing of your business process
-is fully aligned with ASAP and Solution Mgr.

|


 
&'
 Advantages

š Centralized Testing Approach

-Reduce redundancy and inconsistency
-Adhere to standards
-Capture testing metrics and test results
-Maximize managerial visibility and test coverage
-Independent verification test results
š Defects Reporting
-Automatic reporting of defects with quality information
-Prompt defect resolution

|


 
&
|


 
&*