SAP & S/4 Hana Fiori version Overview

 SAP Business Suite 4 SAP HANA abbreviation is SAP S/4 HANA, It means it is the 4th version of SAP Business Suite and it runs only on SAP HANA as per design. 

It is new product with a new code line, the next generation businees suite is built on SAP HANA is advanced in-memory platform, operational database system and it uses modern design principles called SAP Fiori UI, S/4 HANA addresses every functionality of SAP ECC and provides simpliefied data models to decrese the overall system size. It increased performance, better real-time analysis & simplified reporting. 

Compared to other ERP's, SAP is the best option for any business to choose. The massive innovations like IoT, Big Data, Mobile-First. Other simplified features UI, decision making, data model and customer adoption.

SAP Offers an integrated suite of applications that support your end-to-end business processes. The suite helps manage every part of your organization employees, customers, products, spend, finance, and IT.

Business Applications in Lines of Business (LoB) for 25 Industries.

Fiori Overview

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

Next - Generation Uer Experience is SAP Fiori.

SAP Fiori user experience has redefined, the way enterprise users work. When new visual design and appearance, we are making work as more delightful and ready for the next-generation workforce.

SAP Fiori is design system that provides a consistent user experience(UX) of SAP Software across platforms and devices. It is at the core of SAP's product experience and design strategy.

SAP Fiori is the UX of the intelligent Enterprise that changes the way you work. It equips designers and developers with set of tools and guidelines to create apps for any platform faster than ever- providing a consistent, innovative experience for both creators and users. SAP Fiori enables you to turn new ideas into great apps as quickly as the market demands.

SAP S/4 Hana is the market leading intelligent ERP that helps organizations in all industries achieve unparalleled business agility, enabling them to meet ever-rising customer expectations. deliver new products and services, and manage resources more efficiently in an era of increating market and regulator demands.

Fiori Design Principles : 

Fiori Components : 

API Scan Home Menu

You can use the API Scan Home menu to create, edit, run, and export API messages.

The Home menu provides the following options:

 File - Scan an API definition based on files from a file system.

 URI - Scan an API definition based on files from a URI.

 Save as - Save the API Scan project. In the subsequent Save as dialog, enter a file name and click Save. Alternatively, you can click the  Save icon in the top left corner or press CTRL+S. If you have already saved your project previously, API Scan saves it to the same file automatically.

 Open - Open an API Scan project.

 Close - Close the current API Scan project.

 Duplicate - Duplicate the selected folder or message.  Also available in the context menu.

 Delete  - Delete the selected folder or message.  Also available in the context menu.

 Rename - Rename the selected object in the project tree. Also available in the context menu.

 Manage - Open the API Connection Manager.

 Create - Create a connection from API Scan to the API Connection Manager. 

 API TestCase - Export selected messages to Tosca Commander. 

 Scenario - Export selected messages directly to OSV as a Scenario. 

 Update - Update Modules in Tosca Commander when messages change . 

 Request - Show the request of the selected message.

 Response - Show the response of the selected message.

 Cookies - Show cookies, i.e. the domain, name, and value of all stored cookies.

 Add Files - Add a file directly to the message payload or as an attachment .

 Search in Payload - Search the message payload. 

 Validate - Validate the XML structure in the payload.

 Pretty Print - Format the visible message in the Payload tab.

 Word Wrap - Break long text and wrap it into the next line.

Record - Record API messages with the Message Recorder feature.

 Run - Run a message and show the corresponding response.

Benefits Of API Testing in TOSCA

 

1. API testing can be used to validate the core functionalities even when the UI hasn’t been developed/modified. Hence testing can be initiated much before actual functional testing (UI based) is done.
2. Frequent application changes can be tested quickly. 
3. It is easy to maintain test cases in TOSCA.
4. The API testing in TOSCA can be done much faster.
5. Standalone Tosca API Scanning Wizard is available to scan the API in the easiest way.
6. Easy to create Tosca test scenarios.

API Testing menu

 The API Testing menu consists of four sections:

1. Module Attribute

2. Connection

3. Tools

4. Message

Module Attribute

Module Attributes are business-relevant elements of a message, such as a name, ID, or address. Module Attributes allow you to steer the values of these message elements in your TestCase. You can define Module Attributes for the following elements of a message in Tosca Commander:

• Attachments

• Authentication

• Headers

• Method, endpoint, and resource

• Parameters

• Payload

• Status code and response time

The following options are available in the Module Attribute section:

 Add - 

Add Module Attributes. The dropdown menu offers the following options:

• Add Module Attributes with Dynamic List Item(s)

• Add Module Attributes with Static List Item(s)

• Open the Attribute Assistant to add Module Attributes

 Buffer - 

Add and buffer Module Attributes. The dropdown menu offers the following options:

• Buffer Module Attributes with Dynamic List Item(s)

• Buffer Module Attributes with Static List Item(s)

• Open the Attribute Assistant to add and buffer Module Attributes

 Body - 

We can create Body Module Attributes from the elements of a message or the whole body of a message. Use the dynamic menu API Testing to create body Module Attributes from the body of your request message or your response message.

Create body Module Attributes from a request message: 

To add or buffer the body of your request message, follow the steps below:

1. Select the Module and switch to the Technical View.

2. Access the API Testing menu.

3. Click Body and select one of the following options from the dropdown menu:

• To mark the entire payload and add it as a Module Attribute, click Insert Message.

• To mark the entire payload and buffer it as a Module Attribute, click Insert from Buffer.

• To load a payload from file as a Module Attribute, click Load from File ....

  In the subsequent dialog, select a file name and click Open.

Create body Module Attributes from a response message : 

To add or buffer the body of your response message, follow the steps below:

1. Select the Module and switch to the Technical View.

2. Access the API Testing menu.

3. Click Body and select one of the following options from the dropdown menu:

   • To mark the entire payload and add it as a Module Attribute, click Verify Message.

   • To mark the entire payload and buffer it as a Module Attribute, click Buffer Message.

   • To save the payload of your message as a Module Attribute, click Save to File ....

     In the subsequent dialog, define a file name and click Save.

 Validate- 

Check whether the Module Attributes in your API Modules are valid. This can be useful, for instance, if you performed any updates or changes to a Module.

To validate Module Attributes, follow the steps below:

1. In Tosca Commander, select one of the following elements:

   • a Module Attribute

   • an API Module

   • a Module folder that contains API Modules

   • a ComponentFolder that contains API Modules and TestCases

   • the project root element

2. Navigate to the API Testing menu.

3. In the Module Attribute section, click  Validate.

 Update - 

You can use the Update function to update your Module Attributes in one of the following cases:

• Your payload has changed.

• You want to use an existing Module Attribute to steer a different element within the payload.

Tricentis Tosca automatically applies any changes you perform on the Module to the corresponding messages.

To update a Module Attribute, follow the steps below:

1. Select the respective Module Attribute.

   The Technical View displays the current element to be steered in your TestCase.

   The XPath expression in the Properties pane displays the link to the element in the payload.

2. In the Payload tab, highlight the new or changed element with your mouse.

3. Click Update in the API Testing menu.

The system displays the updated XPath expression in the Properties pane.

If you update a body Module Attribute, the system updates the DefaultValue.

Connection

Use the Connection section of the API Testing menu to open the API Connection Manager and to add connections.

You can use the API Connection Manager to manage all your API connections and environments in one place.

The following options are available in the Connection section:

 Manage - Open the API Connection Manager.

 Create  -    Create a connection from an API Module to the API Connection Manager. 

Tools

Use the Tools section of the API Testing menu to open Tricentis Tosca API Scan, open selected Modules in API Scan and to convert OSV scenarios into API TestCases.

The following options are available in the Tools section: 

 API Scan   -  Start API Scan or open selected Modules in API Scan.

 Convert to TestCase  -  Convert an OSV Scenario into an API TestCase.

Message

Use the Message section of the API Testing menu to search message payloads, add files to your message, generate XTestStepValues, and to format the visible message. Additionally, you can update API Modules if the schema has changed.

The following options are available in the Message section:

 Update  -  Update API Modules.

 Add Files  - Add a file to the payload of your message or as an attachment.

 Search in Payload  - Search for strings, regular expressions  and wildcards in the message payload.

 Auto fill Values  - Generate XTestStepValues from the default values of the linked Module or from values pasted from your clipboard.

 Pretty Print  - Format the visible message in the Technical View of the selected Module.

 Word Wrap  -  Break long text and wrap it into the next line in a selected module.

API Testing in TOSCA

 API is the shorter form of Application Program Interface. It’s working as an interface which allows two applications to communicate with each other through common message formats such as, XML, JSON, etc.

Assume, we have four different applications – SAP App, Mobile Apps, Web Portal and Billing System, which are integrated by common interface as API. Here API is working as an interpreter. Each of the system interacting with each other by sending an API request and receiving the API response. Basically, each system is communicating with API and based on the request, API routes the messages to the target system.

Purposes of API:

• Communicate between different applications.
• It’s platform-independent.
• Development of one system is not dependant with another.
• Fast and secure communication.
• Easy to integrate many applications.

Types of API:

REST API (Representational State Transfer): It’s a web service API which is now an essential part of modern web-based applications such as, Facebook, Netflix, etc. REST API should comply with below standards.

• Stateless – It does not allow to store the data they received from a requestor.
• Client-Server Architecture – Client and Server’s REST APIs should be independent with each other.
• Cache – The cache is storing the browsing data for a specific period of time.
• Uniform Interface – Communication should be HTTP requests using URL, CRUD(Create, Read, Update, Delete) and JSON.
• Layered System – REST APIs should use different architecture layers which contributes towards a clear hierarchy.
• Code on demand – It’s an optional rule to transmit code within the application through the API.

RPC API (Remote Procedure Call): These are the simplest API which is used from old days. The aim of RPC is to execute code on the server system. It was easier for application developers to develop applications involving more programs or services in the RPC API.

There are two types of RPC APIs – XML-RPC and JSON-RPC.

SOAP API (Simple Object Access Protocol): It is also one kind of web API. SOAP is the first to define the process about the applications to use a network connection to manage services. It’s a special protocol which is defined by the World Wide Web Consortium (W3C).

API Testing in TOSCA:

The API Testing is an approach to test the API components of any software product in efficient way. To perform API testing, we need to validate the API response received based on the API request. The main moto of API testing is to test the core functionality, reliability, performance and security through the API. API Testing is ideal for testing the core functionality of the application when the all the application is partially developed. So, it allows us to start the testing before the integration of the software components.

The goal of API testing is to ensure that the core functionalities of the application work as expected without interacting in the UI layer. To perform the API Testing, always, we need to take help from any third party tools like Postman, UFT, TOSCA, etc.

Here, TOSCA is one of the best automation tools for API Testing.

Benefits API Testing in TOSCA:

• API testing can be used to validate the core functionalities even when the UI hasn’t been developed/modified. Hence testing can be initiated much before actual functional testing (UI based) is done.
• Frequent application changes can be tested quickly. 
• It is easy to maintain test cases in TOSCA.
• The API testing in TOSCA can be done much faster.
• Standalone Tosca API Scanning Wizard is available to scan the API in the easiest way.
• Easy to create Tosca test scenarios.

Supported Standards for API Testing in TOSCA:

Web Service Standards	SOAP 1.1, SOAP 1.2, REST
Transport Layer	HTTP 1.1, IPv4, IPv6
Message Format	XML, JSON
Message Description Language	OData 4.0, SWAGGER, WSDL 1.1, WADL, XSD, JSON Schema
Authentication	Basic Authentication, Kerberos/SPNEGO, NTLM

Process flow for API Testing in TOSCA:

API Services – Identify the API details and functional flow for automation.

API Scan – Scan the API and create Tosca modules.

Create Test Case – Generate test cases and perform cleanup with parameterization.

Run – Execute the test cases and share the reports to stack holders.

Step by Step Guide to Perform Automation of API Testing in Tosca:

Step1# Collect API Details – We need to collect below API Information of the sample application,

• Endpoint: http://webservice.toscacloud.com/rest/swagger/docs/v2
• Credential: Username1/Password1
• Web Service Standards: REST
• Message Format: JSON

Step2# Identify Scenarios and data formats for the API Request.

Test Scenario – After logging into the sample swagger application, need to add a new coffee brand and verify.

Data Format – Data need to be passed through JSON format.

Step3# Manually Verify the scenario using tools like TOSCA.

Step4# Scan the API with the endpoint reference. 

1) Open the API Scan wizard from “API Testing” tab available in TOSCA Header section.

2) Click on URI button and enter the endpoint address. Now click on OK to start scanning.

3) After a few moments, API scan will be completed, and scanned API modules are displayed in the API Scan Wizard.

Step5# Create modules and test cases – Selecting the root folder, i.e. “Swagger Demo CoffeeShop V2”, click on “API Test Case” to generate modules and test cases in the TOSCA. For every transaction, there are two parts – one for request and another for the response.

Step6# Cleanup scenarios: Auto-generated test cases can be used as a base suite which needs to be cleaned by removing the unwanted folders, create module attributes to parametrize the response values such as, authentication token which will be required to perform any transaction.

Post Coffee (Modules for API Request) –

After assigning the parameters, the API Test Case will look like below.

`

Step7# Execute API Test Case in TOSCA – First of all, we need to add the newly created test case into the execution list. Now, the execution can be initiated by clicking on “Run” button. As it’s an API Testing, no application UI will be visible through out the execution. After completion of execution, Report will look like below.