Date post: | 21-Oct-2015 |
Category: |
Documents |
Upload: | mark-anthony-palma |
View: | 24 times |
Download: | 2 times |
© 2011 SAP AG. All rights reserved. 1
Opportunity Roadmap - Fact sheet
Date
<Opp.name> <Client name>
Business Situation (facts), Their Problem, Impact, Need to Act; What if they do nothing?
Clients Need To Act
Management Sponsor of MU
Responsible Consulting Manager
Opportunity Team (+ Role) N.N. (Bid Manager) N.N. (Solution Architect) N.N. (Industry Expert) N.N. (…)
Customer Responsible (GAD, GAM, AE, CEM/CP)
N.N.
Organization of Opportunity Team
abc…
Actual Status/Results
1. …
2. …
Solution ScopeField Service Value PropositionSAPs USPs (differentiators)
Overview of our Offer
abc…
Risks/ Threats
Next Steps
1. ….
Competitors
Price-/Project Type Fixed Price
Margin X%
GD Days X days
* 1.000 EUR
lastchange
Closing Month
Opp OwnerMastercodeCurrent Phase
CompanyOpp / Pipe ID
35 %Probability (personal
judgment)
Solution Fit
Customer Feedback
Conditions/Budget
Staffing/Delivery
X €Education Revenue
nameInvolved Partner
G
Y
R
R
SAP CONFIDENTIAL SAP IT Test ManagementSAP Solution Manager Test Case Management
Client
Project Name SAP IT Global Production Management Central Test Coordination
Opportunity Owner
CEM / CP
AE / AM
Date 01 / 2008
© 2011 SAP AG. All rights reserved. 2
Learning Objectives
As a result of this presentation, you will be able to:
Structure and create test cases
Assign and maintain Test Cases in a given business blueprint structure
Explain the difference between several kinds of test cases
© 2011 SAP AG. All rights reserved. 3
Content
1. Test Case
2. Manage Test Cases
3. Excercise
© 2011 SAP AG. All rights reserved. 4
1. Test Case
Testing Aspects
Functional Test verification if the system works as designed. Functional tests are e.g. black and white box tests, data flow
tests or simulations of data input. The functional test goes along the business process. Critical processes and fragile functions shall be tested in more detail and more intense.
Load-, Performance Test verification if the system is performing and capable to bear the load.
Besides the performance aspect of every single test case there shall be dedicated performance tests during the integration test phase. A&IS will order on demand VTO (volume test optimization service).
Security and Authorization Test verification if the security and authorization concept is working. Reviews with SAP IT security shall help
identifying the testing scope here.
Test series are dedicated to one aspect.
Each test shall cover always all testing aspects (the focus is on one).
© 2011 SAP AG. All rights reserved. 5
1. Test Case
Testing Scope
The test scope aligns withBusiness Process based on business blueprint Test cases shall be provided for all scenarios, processes, functions and application components. The test case density and coverage shall be increased for the most critical processes and most complex
functions.
User Organization Geographical (US, EMEA, DE, UK, ..) Organizational (FI, Development, Marketing)
User Roles Authorizational Roles (Super user, Power user, Admin, End user) Functional Roles (Customer, Agent)
© 2011 SAP AG. All rights reserved. 6
1. Test Case
Test Case Structure (see Test Case Template as SAP Portal /it-testing)
Test Case Purpose General description of the test case and it’s objective.
General Prerequisites Test Data, Master Data Authorization required Test System
Test Case Step Sequence Use Prerequisites Procedure Result
Final Test Result Expected result for a positive test Output data created for further test cases
eCatt specific data for Test Automation Test Data container Variants
© 2011 SAP AG. All rights reserved. 7
1. Test Case
Test Case Template SAP Portal: Test Case Template (Quick Link: /it-testing)
© 2011 SAP AG. All rights reserved. 8
1. Test Case
Manual vs. Automated Testing
Manual Testing After the creation of test case descriptions, the actual
testing is performed manually by testers. The result of each test case is recorded manually.
No test automation tools are being used.
Test management tools can be deployed for test administration and test organisation.
Automated Testing After the creation of test case descriptions, the actual
testing is performed by automated test tools.
After the test, the result of each test case is recorded automatically by the test tool. Clear and detailed test run records
Test cases can be reused for later purposes (e.g., Support Packages) Regression Testing
Methodical approach to reduce costs and safeguardthe software lifecycle process.
© 2011 SAP AG. All rights reserved. 9
2. Manage Test Cases
Configuration Phase →Test Case Assignment
Configuration PhaseIn configuration phase (SOLAR02) the blueprint structure is frozen
Assign test cases to structure Test cases are assigned to each scenario, process (e.g., for integration testing) or even process step (e.g., for unit testing)
Naming Convention shall be adheredRemote system for Test Case
Technical Name Test Case Name
eCatt Variant Transcation/ Program referenced
© 2011 SAP AG. All rights reserved. 10
2. Manage Test Cases
Test Case Types in Solution Manager
There are different test case types to assign: Test Document (e.g., Upload of a Microsoft Word document and stored in Knowledge Warehouse of
Solution Manager) eCATT Test Configuration (automated / regression testing) CATT (automated / regression testing) – NOT RECOMMENDED External Application – NOT RECOMMENDED Manual Test Case (SAPscript) – NOT RECOMMENDED
To create a new test case select a type from the list and maintain the name.
© 2011 SAP AG. All rights reserved. 11
2. Manage Test Cases
Features of the Type “Manual Test Case”
Test Case Type Manual “Test Document”
Repository Knowledge Warehouse (KW)
Document Any Document – typical WORD format (.DOC)
Work area SolMan or File Share
Create Create in SolMan or Upload File
Change Change in SolMan or Upload changed file
Reference Copy or reference other KW-documents
Where-used Projects
Version Mgt Full KW supported
History OK
© 2011 SAP AG. All rights reserved. 12
2. Manage Test Cases
Manual Test Case
Manual Test Cases are normal KW documents located in the “KW Folder” of the project.
The use in a project is reference to the KW-”project”. Deleting a line in the project does not delete the test case.
A:
Attributes
Test Script File
A:
Attributes
Test Script File
Scenario 1
Process 1.1
Process Step 1.1.1
Process Step 1.1.2
Process 1.2
Process Step 1.2.1
……
© 2011 SAP AG. All rights reserved. 13
2. Manage Test Cases
Test Document
Naming Convention for Test Case Title: <Level> <Area> <Name>
Level: SC = ScenarioPR = ProcessST = Process Step
Area: e.g. CRM, FI, CO, HR,…
Test Case Attributes (button ): Change the Title Maintain a Test Case Status and Keywords Comments History
© 2011 SAP AG. All rights reserved. 14
2. Manage Test Cases
eCatt Test Configuration
The eCatt Test Configuration consists of:Test Script (logic)
Test Data and Variantsimport, export parameters
System Data - systems to execute the script at
Z_1:Test Configuration
Attributes
Test Script
Test Data
System Data
Z_1:Test Configuration
Attributes
Test Script
Test Data
System Data
Scenario 1
Process 1.1
Process Step 1.1.1
Process Step 1.1.2
Process 1.2
Process Step 1.2.1
Test Workbench
Z_2
Z_2
Z_1
Z_1
Script
Test Data
System Data
……
© 2011 SAP AG. All rights reserved. 15
3. Exercises
Scope
Maintain and assign Test Cases in a given Business Blueprint structure
© 2011 SAP AG. All rights reserved. 16
3. Exercise
Configuration
Task: Maintain configuration in TA SOLAR02
Project: I_Test–<Team Number>
1 Open your project.
2 Create a new test case (‘Test Document’) using the default template
3 Upload several test cases from the share\\dwdf073\itac\Public\Test@SAP-IT\CentralTestCoordination\Documentation
4 Assign a test object (Transaction).
5 Change some of your documents
6 Check “where used”
© 2011 SAP AG. All rights reserved. 17
Questions?
Q&A
Thank You!
Contact information:
F name MI. L nameTitleAddressPhone number