CIRC4Life Integration Testing Scenarios
General
This document contains the Integration Testing scenarios between components of the CIRC4Life IT system.
Components involved in Integration Testing
| Module | URL | Developed by | Status |
|---|---|---|---|
| 1.1 Access Control Manager | Link | ICCS | Implemented |
| 1.1.1 ICT Web Services | Link | ICCS | Implemented |
| 1.1.2 Data Gateway | Internal process | ICCS | Work in progress |
| 2.1 Data Entry Tool for Stakeholders | Link | ENV | Implemented |
| 2.2 Intermediate Products Data Export Web Service | Link | ENV | Implemented |
| 3.2 Traceability Module | Link | EECC | Implemented |
| 3.3 LCIA ReCiPe Score Module | Not Available | NTU | Cancelled |
| 4.1 Eco Account and Shopping Module | Native Mobile Application | NTU | Work in progress |
| 4.2 Retailer Tool for Eco Accounting | To Be Announced | NTU | Work in progress |
Integration Testing scenarios
The Integration Testing scenarios are based on the user and system requirements that are described in the Deliverable 4.1 and on the information data flows as described in ICCS development website page for System Architecture.
The following table summarizes all the integration tests that should be performed and pass in order to have a working system. The list is ordered from the integration tests requiring the least dependencies to the ones requiring previous tests to have passed or more components in working order. For example the first 5 tests only require the 1.1 Access Control Manager to be ready and the its clients to be able to perform simple HTTP requests for authorization. The latter tests require more functionality from various components to be ready. The test list is not exhaustive, each test groups the context of a series of tests that need to pass in order to mark the integration between the corresponding components as PASS.
| Integration Test | Components involved | Short Description |
|---|---|---|
| IT #1 | 1.1 Access Control Manager/2.1 Data Entry Tool for Stakeholders | 2.1 Login Screen |
| IT #2 | 1.1 Access Control Manager/3.1 Recycle and Reuse Module | 3.1 Access to ICT Platform Web Services |
| IT #3 | 1.1 Access Control Manager/3.2 Traceability Module | 3.2 Access to ICT Platform Web Services |
| IT #4 | 1.1 Access Control Manager/4.2 Retailer Tool for Eco Accounting | 4.2 Access to ICT Platform Web Services |
| IT #5 | 1.1 Access Control Manager/4.1 Eco Account and Shopping Module | 4.1 Eco-account Login |
| IT #6 | 2.2 Intermediate Products Data Export Web Service/1.1.2 Data Gateway | 2.2 service produces valid export for 1.1.2 to consume |
| IT #7 | 1.1.1 ICT Web Services/3.2 Traceability Module | 1.1.1 REST API service compatible with 3.2 requirements |
| IT #8 | 1.1.1 ICT Web Services/4.1 Eco Account and Shopping Module | 1.1.1 REST API service compatible with 4.1 requirements |
| IT #9 | 1.1.1 ICT Web Services/4.2 Retailer Tool for Eco Accounting | 1.1.1 REST API service compatible with 4.2 requirements |
IT #1: 1.1 Access Control Manager/2.1 Data Entry Tool for Stakeholders
Description
The 2.1 Data Entry Tool for Stakeholders Web Application should integrate with 1.1 Access Control Manager for user authentication and authorization.
Requirements
- 1.1 should be configured to accept OpenID authentication requests from the deployed version of 2.1. The client ID and user credentials should be agreed between ENV and ICCS.
IT #2: 1.1 Access Control Manager/3.1 Recycle and Reuse Module
Description
The 3.1 Recycle and Reuse Module Web Service should integrate with 1.1 Access Control Manager for user authentication and authorization. The process is explained in detail in ICT Platform REST Web Services Usage.
Requirements
- 1.1 should be configured to accept OpenID authentication requests from the deployed version of 3.1.
- 3.1 should be able to request and retrieve access tokens from 1.1.
- 3.1 should be able to properly use the access tokens in order to access protected ICT Platform REST Web Services.
Test pass goal
3.1 Web Service back-end obtains a valid set of access tokens from 1.1 and perform successfully REST service API calls on the ICT Platform RecycleModule service.
IT #3: 1.1 Access Control Manager/3.2 Traceability Module
Description
The 3.2 Traceability Module Web Service should integrate with 1.1 Access Control Manager for user authentication and authorization. The process is explained in detail in ICT Platform REST Web Services Usage.
Requirements
- 1.1 should be configured to accept OpenID authentication requests from the deployed version of 3.2.
- 3.2 should be able to request and retrieve access tokens from 1.1.
- 3.2 should be able to properly use the access tokens in order to access protected ICT Platform REST Web Services.
Test pass goal
3.2 Web Service back-end obtains a valid set of access tokens from 1.1 and perform successfully REST service API calls on the ICT Platform RecycleModule service.
IT #4: 1.1 Access Control Manager/4.2 Retailer Tool for Eco Accounting
Description
The 4.2 Retailer Tool for Eco Accounting Web Service should integrate with 1.1 Access Control Manager for user authentication and authorization. The process is explained in detail in ICT Platform REST Web Services Usage.
Requirements
- 1.1 should be configured to accept OpenID authentication requests from the deployed version of 4.2.
- 4.2 should be able to request and retrieve access tokens from 1.1.
- 4.2 should be able to properly use the access tokens in order to access protected ICT Platform REST Web Services.
Test pass goal
4.2 Web Service back-end obtains a valid set of access tokens from 1.1 and perform successfully REST service API calls on the ICT Platform RecycleModule service.
IT #5: 1.1 Access Control Manager/4.1 Eco Account and Shopping Module
Description
The 4.1 end-user mobile application should be able to initiate a session login with a registered user’s Eco-account credentials by posting to the EndUserModule login endpoint. The session should be easily terminated via the logout endpoint.
IT #6: 2.2 Intermediate Products Data Export Web Service/1.1.2 Data Gateway
Description
2.2 Web Service exports data in the database back-end or 2.1 data entry tool. The format and validity of the data should reflect the original input data and the 2.2 should be able to serve HTTP requests for retrieving them as JSON formatted records. Updates of older data should be possible. 1.1.2 should be able to retrieve new or updated data for every product record in the 2.2 database.
Requirements
- 2.2 exports proper data from the database updated from user input in 2.1.
- 1.1.2 service retrieves data entry records from 2.2.
IT #7: 1.1.1 ICT Web Services/3.2 Traceability Module
Description
3.2 accesses user Eco-accounts via registered Recycle bin User ID, Eco-credits for products based on ID or type, user’s purchase history for recycle item validation, supported product types from ICT Platform services and finally 3.2 can post the recycle company evaluation report on an item found in the recycle bin in order to map it to the user’s Eco-account.
Requirements
- 3.2 retrieves from 1.1.1 purchase history of recycle bin user ID.
- 3.2 retrieves from 1.1.1 Eco-credit from evaluated recycled product.
- 3.2 retrieves from 1.1.1 Eco-credit estimation.
- 3.2 Posts to 1.1.1 Consumer and Product ID with recycle company evaluation result and recycle bin user’s Eco-credits are successfully updated.
IT #8: 1.1.1 ICT Web Services/4.1 Eco Account and Shopping Module
Description
A successful login should initiate a proper session by returning a set of valid access tokens to the 4.1 mobile application. As long as these tokens have not expired and as long as they are timely refreshed, the mobile application can use them in order to request Eco-account and Product information from the ICT Platform EndUserModule.
Requirements
- 4.1 access to logged in user’s Eco-account.
- 4.1 access to Product Master Data information.
Test pass goal
A valid set of access tokens after user login can be used to access endpoints of ICT Platform EndUserModule.
IT #9: 1.1.1 ICT Web Services/4.2 Retailer Tool for Eco Accounting
Description
4.2 is the component for retailers. It should be able to get an anonymized Eco-account user ID from ICT Platform EndUserModule and use it for updating the user’s balance with new purchases and Eco-debits via ICT Platform RetailerModule. This scenario involves also the mobile application of 4.1, where the user logins to his Eco-account and provides the retailer module service with the anonymous user ID, via text or QR code. Next, the retailer module uses this anonymous user ID in order to access the Eco-account balance. Finally the retailer modules has Master Product Database access for retrieving product details that can be shown to consumers in order to make educated purchases.