Skip to content

7. Systemtestreport

Jump to bottom
UdolfSeelenfrost edited this page May 19, 2021 · 31 revisions

Contents

1. Changelog

Version Date Author Comment
0.1 29.4.2021 Johannes Timter created
1.0 14.5.2021 Johannes Timter finished

2. Introduction

The Systemtestreport (STR) is based on the Testsuites and Testcases defined in the Systemtestplan (STP). It describes the preconditions, the actions and the results of the execution of the Testcases. Deficiencies can be found, documented and eventually fixed through the STR.

3. Definitions

TC Testcase

TS Testsuite

GUI Graphical User Interface

4. Test Objects

Ref.-Id. Test Object Name product-number, serial-number, modification status
1 AML Database Management Graphical User Interface Build v1.0 beta
2 AML Database Management REST API Build v1.0 beta

5. Test Equipment

The following equipment is required to execute the tests:

  • A PC with Windows 7 or higher
  • Installed AutomationML Editor (Download)
  • Internet Access and a current version of Google Chrome, Mozilla Firefox or Microsoft Edge
  • To test the REST API, the program Postman is required. (Download)

6. Results of Testsuite <TS-001: Graphical User Interface>

6.1 Results of Testcase <TC.GUI.001.F> (Installation and Setup)

Testcase ID: TC.GUI.001.F
Testcase Name: Installation and Setup
Requirement ID(s): LF10, LF50
Description: The test case verifies that the GUI displays basic information about the uploaded aml files and offers the user access to the baisc functions for aml files
Step Action Expected Result Actual Result
1 Install the AML NoSQL Database Manangement on your local machine. Use npm start to start to install the components. Open the GUI by using your preferred browser to open localhost:4200 Installation and Startup finishes successully. The homepage of the AML NoSQL Database Manangement tool is displayed Installation and Startup succeed and we can see the homepage.
2 Enter Username "Username" and Username "Password" Password. Press login. You are redirected to the main page Login works, main page is displayed
3 Click on the user icon on the right side of the navbar and verify that you are logged as LMF A popup appears, stating that you're logged in as "LMF", as well as a Logout button Popup with current user name and logout button appears

Tested by: Johannes Timter, Date: 14.5.2021, Result: SUCCESS

6.2 Results of Testcase <TC.GUI.002.F> (File upload)

Testcase ID: TC.GUI.002.F
Testcase Name: File upload with valid file
Requirement ID(s): LF10, LF20
Description: The test case verifies that the system allows the user to upload .aml and .xml files to the database
Step Action expected Result actual Result
1 Go to the homepage and click the "Upload" button on the top right side. "Upload file" dialogue window opens The expected dialogue window opens
2 Scroll down the page and take a look at the displayed files that are listed in the table Every uploaded file is displayed in the table. The following information is displayed about each entry/file in the table: ID, Filename, Filesize in bytes, Upload Data. Information about the uploaded file is displayed in the table
3 Take a look at the right edge of an entry in the file table The following buttons should be available to click: Edit, Download, Delete. On hovering over the buttons, a tooltip should show up The expected buttons are visible, the tooltips are displayed after hovering
4 Use the "Datei auswählen" button to open the file selection dialogue. File selection dialogue window opens The expected dialogue window opens
6 Here, select an .aml or .xml file and click "open". See Testdata table for expected Result See Testdata table for actual Result

Testdata:

Dataset File is Valid expected Result actual Result
1 Balluff_ProductLibrary_CAEX3_221020.aml valid "Upload Successful" popup shows up, and the file is displayed in the table. "Upload Successful"
2 03_Verzweigungen_Schleifen.pdf invalid "Upload Failed" popup shows up, the file doesn't show up in the table. "Upload Failed"

Tested by: Johannes Timter, Date: 19.5.2021, Result: SUCCESS

6.3 Results of Testcase <TC.GUI.003.F> (Search for files)

Testcase ID: TC.GUI.003.F
Testcase Name: Search for files
Requirement ID(s): LF10, LF40
Description: The test case verifies that the system allows the user to search for uploaded files using the name

Test Steps:

Step Action expected Result actual Result
1 Upload files with the following names: "TINF19C_AML_Library.aml" and Balluff_ProductLibrary_CAEX3_221020.aml Files are uploaded successfully File uploads are successful
2 Use the "Filter" text field on the top left side of the home screen and enter the given search term Results are filtered according to the search term See Testdata table for actual Result

Testdata:

Dataset Searchterm is Valid actual Result
1 Library valid, 2 results 2 Results
2 TINF19C_AML_Library.a valid, 1 result 1 results
3 adasdasdas dqwqwdqwd qwdqw valid, 0 results 0 result
4 Balluff_ProductLibrary_CAEX3_221020.aml valid, 1 results 1 result
5 <empty String> valid, 2 results 2 results

Tested by: Johannes Timter, Date: 19.5.2021, Result: SUCCESS

6.4 Results for Testcase <TC.GUI.004.F> (Download files)

Testcase ID: TC.GUI.004.F
Testcase Name: Download files
Requirement ID(s): LF10, LF50, LF60
Description: The test case verifies that the system allows the user to download files

Test Steps:

Step Action Expected Result Actual Result
1 Filter for a file with the following name: "Balluff_ProductLibrary_CAEX3_221020.aml" Expected File is displayed in table We can see the expected file
2 Click the "Download" icon on the right side of the file entry The file download starts through the browser Download starts
3 Wait for the download to finish The file is downloaded through the browser. "File downloaded successfully" popup appears briefly. Download finishes, successfully

Tested by: Johannes Timter, Date: 19.5.2021, Result: SUCCESS

6.5 Result for Testcase <TC.GUI.005.F> (Edit saved file)

Testcase ID: TC.GUI.005.F
Testcase Name: Edit saved file
Requirement ID(s): LF10, LF50, LF70
Description: The test case verifies that the system allows the user to edit files

Test Steps:

Step Action Expected Result Actual Result
1 Click the "Edit" icon on the right side of a file entry The "Edit file" dialogue opens. Expected dialogue opens
2 Click on the "Name" field and change the name of the file Filename changes within the "Edit file" dialogue Expected dialogue opens
3 Click on the "content" field and change the content of the file The file content changes within the "Edit file" dialogue Content changes as expected
4 Click on the "Upload" button in the bottom right corner The changes are uploaded to the database "File uploaded successfully" snackbar appears
5 Open the edited file again in an edit window The changes that have been applied can be observed The changes from step 3 are still applied.
6 Repeat steps 1-3 - -
7 Click on the "Cancel" button in the bottom right corner The "Edit file" dialogue closes and no changes are committed to the database The dialogue closes
8 Open the edited file again in an edit window Confirm that the changes have not been applied The file is still in its original state

Tested by: Johannes Timter, Date: 19.5.2021, Result: SUCCESS

6.6 Testcase <TC.GUI.006.F> (Delete files)

Testcase ID: TC.GUI.006.F
Testcase Name: Delete files
Requirement ID(s): LF10, LF50, LF80
Description: The test case verifies that the system allows the user to delete uploaded files

Test Steps:

Step Action Expected Result Actual Result
1 Upload a file using the previously described upload function The file is uploaded and displayed within the table File is uploaded and visible in table
2 Click on the "Delete" icon of the file File is deleted from the database. File disappears from the table. Popup with "File deleted successfully" appears briefly Popup appears as expected and file is no longer visible in table

Tested by: Johannes Timter, Date: 19.5.2021, Result: SUCCESS

6.7 Results for Testcase <TC.GUI.007.F> (Info page)

Testcase ID: TC.GUI.007.F
Testcase Name: Info page
Requirement ID(s): LF10, LF50, LF90
Description: The test case verifies that info page display a short tutorial for the user

Test Steps:

Step Action Expected Result Actual Result
1 In the navigation bar, click in the "i" Icon The "Info und Tutorial" page is displayed. You can see basis instructions on how to use the AML NoSQL Database Manangement site Info Page appears

Tested by: Johannes Timter, Date: 19.5.2021, Result: SUCCESS

6.8 Results for Testcase <TC.GUI.008.F> (File Roundtrip)

Testcase ID: TC.GUI.008.F
Testcase Name: File Roundtrip
Requirement ID(s): LF10, LF20, LF60, LF100
Description: The test case verifies that a valid .aml file survives the roundtrip through the system (upload and download) and continues to be valid.

Test Steps:

Step Action Expected Result Actual Result
1 Open the AutomationMLEditor and import your .aml vile. Verify the files validity. The file is valid File is displayed in the Editor and is valid
2 Open the AML Database management site and upload your file as explained in TC.GUI.005.F The upload is successfull Upload succeeds
3 Download the file that has just been uploaded, by clicking on the download icon on the respective file The download is successfull Download succeeds as well
4 Open the AutomationMLEditor and import the downloaded vile. Verify the filex validity again The file is valid File is displayed in the Editor again and is still valid. File content has not changed.

Tested by: Johannes Timter, Date: 19.5.2021, Result: SUCCESS

7. Results for Testsuite <TS.REST>: REST API>

7.1 Results for Testcase <TC.REST.001.F> (GET calls)

Testcase ID: TC.REST.001.F
Testcase Name: GET calls
Requirement ID(s): LF110, LF100, LF30
Description: The test case verifies that the REST API GET calls work as documented in the SRS

Test Steps:

Step Action Expected Result Actual Result
1 Use the GUI to upload two files Two files from testdata are uploaded and visible in the table in the home page The files are uploaded and visible.
2 Open Postman and send the following GET request: localhost:3000/file The two files that are present in the database are returned in the format as seen below, along with HTTP-Code 200. The two files are returned in the JSON response. HTTP-Code is 200.
3 Send the following GET request: localhost:3000/file/id={mongoDBID}, where {mongoDBID} is the _id attribute of the first file that has been received in step 2 Verify that only the first uploaded file is returned in the format below, along with HTTP-Code 200. Only the file specified witht he id query parameter is returned

Tested by: Johannes Timter, Date: 19.5.2021, Result: SUCCESS

7.2 Result for Testcase <TC.REST.002.F> (POST call)

Testcase ID: TC.REST.002.F
Testcase Name: POST call
Requirement ID(s): LF110, LF100, LF30
Description: The test case verifies that the REST API POST call works as documented in the SRS

Test Steps:

Step Action Expected Result Actual Result
1 Open Postman and send the following POST request: localhost:3000/file and use the Testdata below as body Verify that you receive a JSON response containing "status": "success", as well as the just object that hast just been added "status": "success" and the object from the testdata is received in JSON format
2 Send the following GET request: localhost:3000/file Verify that the file is now present in the database The POSTed file is among the received files

Tested by: Johannes Timter, Date: 19.5.2021, Result: SUCCESS

7.3 Results for Testcase <TC.REST.003.F> (DELETE call)

Testcase ID: TC.REST.003.F
Testcase Name: DELETE call
Requirement ID(s): LF110, LF100, LF30
Description: The test case verifies that the REST API DELETE call works as documented in the SRS

Test Steps:

Step Action Expected Result Actual Result
1 Use the GUI to upload two files Two files are uploaded and visible in the table in the home page The files from testdata are uplaoded successfully
2 Open Postman and send the following GET request: localhost:3000/file. Remember the _id attribute of one of the files - One of the _id attributes is written down
3 Send send the following DELETE request: localhost:3000/file/id={mongoDBID}, where {mongoDBID} is the _id attribute of the first file that has been received in step 2. You receive "status": "success" as well as the deleted file in the format below, along with HTTP-Code 200. "status": "success" and the deleted file are received
2 Send the following GET request: localhost:3000/file Verify only the not deleted file is not returned anymore, along with HTTP-Code 200. Deleted file is not contained in the returned files anymore

Tested by: Johannes Timter, Date: 19.5.2021, Result: SUCCESS

7.4 Results for Testcase <TC.REST.004.F> (PUT call)

Testcase ID: TC.REST.004.F
Testcase Name: PUT call
Requirement ID(s): LF110, LF100, LF30
Description: The test case verifies that the REST API PUT call works as documented in the SRS

Test Steps:

Step Action Expected Result Actual Result
1 Open Postman and send the following GET request: localhost:3000/file. Remember the _id attribute of one of the files - One of the _id attributes is written down
2 Send the following PUT request: localhost:3000/file/id={mongoDBID}, where {mongoDBID} is the _id attribute of the first file that has been received in step 1. Use the JSON testdata below as body of the PUT request. You receive a JSON response containing "status": "success", as well as the object that hast just been manipulated (name and content) "status": "success", as well as the new name and new content of the file are returned
3 Send the following GET request: localhost:3000/file The content and name of the file have been changed according to the name and content of the testdata. The response confirms that the file with the _id now contains the name and content of the testdata.

Tested by: Johannes Timter, Date: 19.5.2021, Result: SUCCESS

© LMF.software - Jonas Bihr, Namid Marxen, Johannes Emanuel Timter & Nils-Christopher Wiesenauer
For any question regarding our software contact us on here on GitHub.

Clone this wiki locally