Disclaimers: All the information on topics is published for general information purpose only and further to be noted, this material is completely production of authors’ own research contents / material collected from various websites, conference and workshops in a close groups such as Meetup, online webinars, training video, lexical etc. I do not make any warranties about the completeness, reliability and accuracy of this information.
Using SOLAR01 one can create your own business process and you can also assign SAP standard to your project.
Creating Business blueprint document is also posible with this t-code.
Similarly SOLAR02 one can configure and create configuration document for project
OLAR_PROJECT_ADMIN-Create New Project
SOLAR01-Business Blueprint
SOLAR02-Configuration
STWB_2-Test Organizer: Test Plan Management
STWB_WORK-Test Worklist
STWB_SET-Central Test Workbench Setting
STWB_INFO-Status Info System
STWB_1-Test Organizer: Test Catalog Management
SOLMAN_PROJECT-Solution manager Project Overview
SMSY-System Landscape
SOLUTION_MANAGER-Maintenance Optmizer
SOLAR_EVAL-Solution manager Project Analysis
SCOUT-Coustomizing Scout
SOLAR_LEARNING_MAP-Authoring Environment for Learning Map
How to
manage your testing activities with the Test Suite provided by SAP Solution
Manager 7.2
Introduction
SAP offers a powerful test
management tool as part of SAP Solution Manager 7.2: The Test Suite.
As a test manager, tester or
developer, the Test Suite supports you during the whole test management
process. You can use it for test preparation, test execution and test
reporting.
Nevertheless, for the
organizational setup of your test management, you still need a detailed test
concept. The Test Suite is a test management tool with a lot of features. These
features need to be customized and orchestrated by a detailed test management
concept.
You can start the Test Suite via
the well-known launchpad. It is possible to customize the dashboard based on
roles and authorizations. Please see below for an example launchpad for a test
manager.
SolMan 7.2 Test Suite View
The launchpad may be adapted and
streamlined for other roles, e.g. for testers.
Because of its integration in SAP
Solution Manager 7.2, you can use the Solution Documentation features to
structure your test documentation by adding test case documents to the existing
solution documentation nodes.
Then you gather all needed test
cases and add them to a test plan, e.g. all needed test cases for a defined
test phase. Based on this test case selection you create several test packages
and assign them to the testers.
The testers execute the test
cases with the help of a Fiori app. Once they find an error, they may create
incidents. The incidents are routed to the developers to analyse and fix them.
As a test manager, you can use
the powerful reporting tools in the Test Suite. For example, all relevant data
is presented in the Test Suite Dashboard.
ProcessHierarchy for test case navigation
Test
Preparation
When using the Test Suite for
test management, a well-defined solution documentation is key. The solution
documentation is the baseline for your testing activities. The test case
documents are maintained in the business process structure. Function test cases
are attached more to process steps whereas E2E test cases would be attached to
scenarios.
Test Plan attribute
When you start to plan your test
phases, you start the Test Plan Management application with the tile “Test Plan
Management” from the launchpad. Then you create a new test plan and select all
needed test cases from the solution documentation. After this, you add them to
a so-called test plan. From the test plan, you create test packages and
distribute them to your tester community. Each tester may receive more than one
test package.
First you must add some general
administrative data to the test plan, e.g. the ID and the description.
The settings like the release
schema or the start and end dates must be defined.
To get access to the selected
test cases from the solution documentation, the test case hierarchy has to be
generated.
Once this is done, the test cases
from the solution documentation may be selected.
Now the test cases from the test
plan have to be assigned to the testers. This is done by creating test
packages.
Test Execution
Once a tester was assigned to a test package, he may access the test package from the Tester Worklist. This list contains all test cases that shall be executed, structured by test packages
Within the Tester Worklist, the testers have instant access to both the test case and to the object to be tested, e.g. a SAP GUI transaction or a Fiori application.
In case the tester detects an error during the testing efforts, he can create an incident from the Tester Worklist. In the incident he should document all relevant information like the steps to reproduce or screenshots. Once created, the incident is routed to the relevant developer.
As soon as the incident is solved, the tester may re-test the test case in the Tester Worklist.
Based on the test case selection
of the underlying test plan, the test cases for the test packages are selected.
Finally, the dedicated tester(s)
are assigned to the test package.
test
Reporting
Already during the test execution
phase, you can create reports. You may measure the test progress or the status
of created defects. Please see below for a complete list of test reports
available in the standard Test Suite.
As an example, the Test Suite
Dashboard (i.e. “KPIs Manual Testing”) provides you with real-time data about
the currently running test phase.
The reporting features a bunch of
metrics for an operational reporting during the test phases, e.g. checking the
progress within test plans. In addition to that, the reporting features may
also be used for management reporting, e.g. creating a detailed test report as
a Word document.
As you
understand -SAP Test Acceleration and Optimization is designed for
SAP-GUI-based applications. SAP Test Acceleration and Optimization users should
be experienced quality managers who are familiar with the SAP Quality Center
application by HP, SAP GUI ERP applications, and business process testing.
Lets see first the SAP TAO Functional Blocks
Integration
The SAP Test Acceleration and Optimization
application requires products from SAP and SAP Quality Center.
The SAP Test Acceleration and Optimization client
application runs on a Microsoft Windows system. It performs three key
functions: inspecting the transactions from an SAP server, exporting the
transactions to SAP Quality Center, and consolidating the components or scripts
from SAP Quality Center.
1 - Inspection
Inspection captures the data in a screen or
transaction and determines its validity. It enables you to add, maintain, and
delete a list of transactions and screens from this list.
The SAP Test Acceleration and Optimization application
has two modes of inspection.
The Inspection tab page in the SAP Test
Acceleration and Optimization client enables you to select multiple SAP GUI
screens and transactions for testing, in an easy-to-use interface. It then
determines whether these screens and transactions are valid, and sends the
valid screens to SAP Quality Center.
The UI Scanner tab page collects information
from one screen at a time, and sends screen objects to SAP Quality Center, as a
component. The UI scanner scans all objects on the screen including dynamically
generated objects. The UI scanner requires an active QuickTest Professional
installation on your local work station.
Process flow analyzer
The process flow analyzer (PFA) records all user
interactions and the sequence of screens to execute a business process, in the
SAP Test Acceleration and Optimization repository. It automates inspection and
creation of components.
1.1 Repository
The SAP Test Acceleration and Optimization
repository is part of the SAP Solution Manager system, and is used to store the
following.
User interactions and the sequence of screens in a
business process
Information specific to SAP Test Acceleration and
Optimization that cannot be retrieved by other tools
Results or states during process flow analysis,
before the component is created
The SAP Test Acceleration and Optimization
repository comprises the following.
1.2 Component explorer
The component explorer views the list of components
in a domain and project.
2- PFA
explorer
The PFA explorer views the list of analyses
performed by PFA.
3-
Import/export
Import/export usually runs in the background, to
transfer data from the SAP Test Acceleration and Optimization client to SAP
Quality Center. It is also helpful for maintenance functions, such as moving
components from server to server or from project to project. The import/export
module does the following.
Export components from the inspector in the SAP
Test Acceleration and Optimization client to SAP Quality Center
Import components from SAP Quality Center to the
SAP Test Acceleration and Optimization client
Export a component from the UI scanner and send it
to SAP Quality Center, in the background
4-
Consolidation
Consolidation gathers all the objects and data in
an SAP Quality Center test, and creates a single component. If you
reconsolidate this component, you get a component that contains all the code
and screen elements in a test. It executes much faster than the individual
components. These consolidated components help you to maintain business
processes.
The parameter of a basic component is available for
a consolidated component only if a value has been set for the parameter before
consolidation. You can edit this parameter even after consolidation. If you add
a parameter to the basic component after consolidation, you need to
reconsolidate the basic component.
Change analysis
Change analysis helps you to analyze the impact of
changes due to upgrades, SAP patches, or custom development on a test,
component, or consolidated component. The impact is found by comparison of
results from the technical bill of materials (TBOM), transport requests and SAP
patches.
This
blog feed is about configuring SAP Test Acceleration and Optimization client
functions and
SAP
Quality Center, and creating an application area in QuickTest Professional. these comonents also form SAP TOA communication channel
select root or create folder for installation
Install the SAP Test Acceleration and Optimization Runtime Library (RTL)
The following instructions apply once only for each new project (a project is an SAP Quality Center project) and only after the first installation of SAP Test Acceleration and Optimization. If you are migrating from SAP Test Acceleration and Optimization 1.0.3 to 1.0.10 or 2.0,.
1. Copy the CBASE_Default folder from the installation folder (by default C:\Program Files\SAP\SAP TAO).
2. Paste the folder into a location that you specified in the Root Path window during installation of SAP Test Acceleration and Optimization.
We recommend that you put this folder in a shared location.
3. Rename the folder to CBASE.
For more information, see admin guide
*******************SAP
TAO Configuration***
As you
understand -SAP Test Acceleration and Optimization is designed for
SAP-GUI-based applications. SAP Test Acceleration and Optimization users should
be experienced quality managers who are familiar with the SAP Quality Center
application by HP, SAP GUI ERP applications, and business process testing.
At
the top right-hand corner of the SAP Test Acceleration and Optimization client,
choose Configuration.
The Configurationscreen
with the following tabs appears.
·License
·Self Test
·Inspect
·Import / Export
·Consolidate
·Log
·PFA
·Expert
·Others
License
SAP
Test Acceleration and Optimization has a different and improved licensing
model. It is server-based. An SAP Solution Manager (with SP 20 or higher)
instance now distributes licenses to the clients. You need to go into
configuration, to set-up this license.
1 If
the SAP Solution Manager system is not displayed on the License tab
page, perform the following sub-steps:
a.
In the SAP Logon add the required SAP Solution Manager system.
b.
On the Licensetab page of the Configuration window, choose Refresh
SAP Logon List.
2 On
the Licensetab page enter the required user credentials.
For
more information on the user and role, referee Securityon
administration guide.
3.
Choose Test SAP Connection.
4.
Choose Check for License, to request a license.
Your
local instance of SAP Test Acceleration and Optimization is now enabled.
You
can use the features of SAP Test Acceleration and Optimization only if the
license is approved.
5.
To retrieve the last saved configuration, choose Restore Connection.
Self
Test
The Self-testtab
page is used to verify the following:
SAP
Test Acceleration and Optimization has been installed
The
configuration file, license and CBASE libraries
The
environment files specified in the configuration file
The
initialization variables specified in the RTL configuration file
The
default components have been uploaded for the quality center project as
mentioned in the PFA tab page
The
system displays the report in the lower half of the Self Test tab
Installing
the SAP Test Acceleration and Optimization Runtime Library (RTL)
The
following instructions apply once only for each new project (a project is an
SAP Quality Center project) and only after the first installation of SAP Test
Acceleration and Optimization. If you are migrating from SAP Test Acceleration
and Optimization 1.0.3 to 2.0 or a higher version, see snd webite for further
help.
1.
Copy the CBASE_Default folder from the installation folder (by default C:\Program
Files\SAP\SAP TAO).
2.
Paste the folder into a location that you specified in the Root Path window
during installation of SAP Test Acceleration and Optimization.
I
recommend that you put this folder in a shared location.
Rename
the folder to CBASE.
For more
information,
Inspect
The Inspecttab
page selects the activities that you want SAP Test Acceleration and
Optimization to perform during inspection and creation
of components.
The
type of component selected determines whether it needs to get data from the
screen (Get) or from a data table (Set).
Select
at least one of the options available. For more information, see Figure
BELOW.
The Get
components save any value of the supported objects in a data table field (DT_). All the parameters in a Get component
are DT_ values.
You
can use these values either to make a comparison or as input to another field.
The
naming convention for Get components is the same as for Set components,
with a suffix of _GET.
Import
/ Export
The Import
/ Export tab page specifies the activities to be performed when
transferring components between SAP Quality Center and SAP Test Acceleration
and Optimization client. A feature of SAP Test Acceleration and Optimization is
the ability to overwrite components each time one is uploaded.
You
can activate the repository synchronization tool, which is a support tool, for
synchronizing the quality center and repository. We recommend that you do not
activate this tool unless requested by SAP.
Consolidate
The Consolidatetab
page specifies the activities to be performed when consolidating test
components. The
options include:
Add
Component Name in Consolidated Script To
put hints in a test script to identify the component used.
Create“EMPTY”
Parameters
To
create an empty parameter representing all the parameters that have no value.
For more
information,
PFA
On
the PFAtab page, you perform the basic settings for PFA.
Test
Folder Path
you
specify the location for the tests in the SAP Quality Center created using the
PFA.
Default
Component Path you
specify the location of default components in the SAP Quality Center, which the
PFA uses while uploading the analysis.
Overwrite
Test With Same Name
You
select this option if you want the new test of a transaction to replace an
existing test.
Suffix
for Duplicate Test
Tuesday, 5 June 2012
SAP Solution Manager Transaction Codes
RMMAIN - Roadmap SOLAR_PROJECT_ADMIN -
Project Administration SOLAR01 - Business
Blueprint SOLAR02 - Configuration STWB_2 - Test Plan
Management STWB_WORK - Testing SOLAR_EVAL - Reporting SMSY - System Landscape SOLUTION_MANAGER -
Solution Manager Operations
