SAP S/4HANA Cloud provides a test tool that can help customers automate their testing during various phases of the projects and also during Quarterly upgrade. This blog will help you understand what’s new in Test Automation Tool in 2005.
Let see the new features released in test automation tool
Test your process app
To use the test automation tool, you need access to test automation tool apps which are “Test Your Process”, “Manage Your Test Process” and “Analyze Automated Test Results”. The apps “Test Your Process”, “Manage Your Test Process” are accessible via role “SAP_BR_BPC_EXPERT” or“SAP_BR_ADMIN_TEST_AUTOMATION”. The app “Analyze Automated Test Results” is only accessible via role “SAP_BR_ADMIN_TEST_AUTOMATION”. The recommended browser is Chrome.
Test Automation Tool set up- Allows selection of the email ID as a user ID
To use the test automation tool, you need to first set up the test tool via app “test your process”. Here you need to add the credentials of an active business user of Quality system to the manage user section of the app. The user login ID depends the customer set up which can be an email ID or an user name or an employee code etc. Initially only user name was selected from the search help. From 2005 release user can now choose to add an email ID if the login ID to quality system is set as email ID.
Access manage user section of the “test your process” app and click on add option to add the user details.
Role Field : The first entry should be with “DEFAULT”. This is mandatory for the test tool to execute. The role here does not mean you need to create a role name called DEFAULT. This role is only linked with standard automate for test execution purpose. To execute the standard automates this entry needs to exist. To do a role based testing you can create more roles and add user. The same role name should be added to the standard automate for test execution.
Description: You can define the purpose of this role like test user or test administrator.
User name or Email ID: The user name here needs to be an active business user with which user can log into SAP S/4HANA Cloud using the same user name. This field is a search help to select the users available in the system.
The highlighted column (refer screen shot) is for email ID now added.
If the log in user of Quality system is set as email ID only then set the switch on. This way it will only take the email ID of the selected user else you can leave it as default setting as no..
Password: The business user which you assign should have the same password with which user logs into SAP S/4HANA Cloud. If you change the password for SAP S/4HANA Cloud, then the password here should also be manually updated as the system does not update the password automatically. If the password is not updated or incorrectly entered, then the test execution will not happen. Based on the customer password policy the system passwords changes frequently depending on customers, it could a month or every quarter. Each time the password changes, it needs to be updated here as well.
Currently test automation tool is supporting SAP Cloud Identity and Microsoft ADFS (Supports only basic authentication with login credentials on the one screen).Please note only single factor authentication is supported for the test automation tool to work. The single factor authentication is in which the user provides only one factor – typically a password. The test automation tool does not support a two-factor authentication methods which rely on users providing a password as well as a second factor, usually either a security token.
Test Plans Scheduling - Allows the user to schedule test plan by defining their own desired time, date and frequency. This features also allows the post upgrade test plans created by SAP to be scheduled.
Access schedule test plan section of the “test your process” app and click on add option to add the test plans
Here you can select the test plans and variant from the search option. The latest executed test plans will appear on top when search option is clicked.
The schedule field shows the options for executing test plan just once in the specified time and date provided by the user.
User can define other option by choosing the frequency once in every week/two weeks or month in the desired time and start & end date provided.
The date field has certain limitations as you cannot choose a date which is in past, the future date cannot be more than six(6) months
If the execution of the test plan is chosen as frequency in every week/two week or month then you would need to enter end date. The end date does not appear if you select execution as just once.
The start time should be schedule at least 65 min ahead of the current time. System will show and error if time is set before 65 min.
Post Upgrade Tests are smoke tests performed in Q-systems of live customers who has given their consent. The PUT is executed during the upgrade weekend, it creates and executes PUT test plans by picking up the latest transactional data or master data on a run time.
These test automates are standard testing and do not cover end to end scenarios of the best practices. PUT testing does not replaces the regression testing.
Once the post upgrade test is performed user can view all the test plans which got created during the process in “test your process” app and the these test plans can now be schedule with desired time and date.
Hence you can schedule 20 test plans as before. Initially you could choose only one test plan at a time but now same test plan can selected multiple times based with different variant for
e.g there is test plan as Sales_Order and this test plans has three (3) variants var1,var2 and var3. You want to execute the test plan with all three (3) variants. The you would add Sales_Order with var1 and again add with Sales_Order with var2 and again add Sales_Order with var3.
Once all the test plans are scheduled the end date would be visible in colours green and red. Green is for active and once the date has passed then it will appear as red.
The schedule test plan feature has gone through a complete change. The existing database is not used anymore. Hence if customer already using the feature and have active test plans after 2005 these test plans will not be visible and rescheduling of test plan is required.