• Changelog
• Scope
• Definitions
• Product Names and Attributes
• Features
• Test Preparation Strategies
• Test Equipment
• Test Schedule
• Testsuite <TS-001> Graphical User Interface
  • <TC-001-001> Basic verification of GUI
  • <TC-001-002> File upload
  • <TC-001-003> Search for files
  • <TC-001-004> Download files
  • <TC-001-005> Edit saved file
  • <TC-001-006> Delete files
  • <TC-001-007> Info page
  • <TC-001-008> File Roundtrip
• Testsuite <TS-001> REST API
  • <TC-002-001> GET calls
  • <TC-002-002> POST call
  • <TC-002-003> DELETE call
  • <TC-002-004> PUT call

The STP (System Test Plan) specifies the test strategy and test planning. It references tests to be performed to verify the accordance of the demanded features given by the SRS (System Requirements Specification) to the implemented features. The document derived from the STP is the STR (System Test Report) where additionally the results are given.

TC Testcase

TS Testsuite

GUI Graphical User Interface

The following requirements must be verified, as long as they are not classified as “not to be tested”. This table shows the test coverage between functionality and test suites or test cases.

Requirement-ID	Description	Priority	Testsuite ID
LF10: Graphical User Interface	The GUI provides the user with information about the saved files and the ability to edit, delete, download or upload files with the GUI	A	TS-001
LF20: Upload files	Upload local .aml files to the server.	A	TS-001
LF30: Conversion from XML to JSON	Uploaded file is converted to a JSON format, so it can be saved in a MongoDB database. One JSON object contains the entire file content as a string.	A	TS-001
LF40: Search for files	-Search for entries by by ID -Filter files by different parameters, e.g. upload date	A	TS-001
LF50: List all files	All saved files are listed for the user. Displayed entries provide access to entry-specific functions listed below	A	TS-001
LF60: Download files	Download a previously uploaded file through the browser.	A	TS-001
LF70: Edit files	Uploaded files can be edited and saved within the browser	A	TS-001
LF80: Delete files	Delete uploaded file from server through a confirmation dialog.	A	TS-001
LF90: Info Page	The Info page lists and explains the functions of the web interface.	A	TS-001
LF100: Database	Files are stored in a MongoDB	A	TS-001
LF110: REST API	The User can access the following functions through a REST API:	A	TS-002

The organisation and preparation of tests will be based on application use cases. We will separate the two ways the user can interact with the application:

• The Graphical User Interface can be accessed through one of the current popular web browsers and contains all functions documented in the SRS. For the management of AML files we provide the user with many functions such as upload, edit, search, download and deletion of uploaded files. Each of these functions needs to be tested by using equivalence classes that contain expected/valid and unexpected/invalid user input/behavior. In case of valid input we expect the GUI to perform the promised action and leave our database in a consistent state. In case of invalid input we expect the user to receive feedback based in his error.
• The REST Api (as described in LF110) provides access to the most basic functions of our product through the classic REST calls GET, POST, PUT, and DELETE. We need to ensure execution of the functions in case of valid input, and at least the return of the correct HTTP-code in case of invalid user input or a backend error.

Since none of the GUI tests interact or block each other, the GUI tests can be executed in an order of choice. The REST API tests should be executed in order as documented, as previously uploaded files are used in subsequent steps.

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)

Deadline for the project is at the end of May 2021. By finishing our Systemtestreport by the end of April we still have an entire Month of time to refactor and correct any detected errors. For the execution of the tests the test-manager will be supported by the system-architect and the product manager.

Test Steps:

Testdata: none

Test Steps:

Testdata: testdata_for_TC.GUI.002.F.zip

Test Steps:

Testdata:

Test Steps:

Testdata:

Test Steps:

Testdata:

Test Steps:

Testdata:

Test Steps:

Testdata: none

Test Steps:

Testdata:

Test Steps:

{
"status": "success",
    "data": {
        "name": "TINF19C_AML_Library.aml",
        "content":  string
    }
}

Test Steps:

Testdata:

{
    "file": {
    "base64": "data:application/xml;base64,ZnVlciBiYWxsdWY=",
    "name": "test-file.xml",
    "size": 560,
    "type": "text/xml"
    }
}

Test Steps:

{
    "status": "success",
    "data": {
        "n": 1,
        "ok": 1,
        "deletedCount": 1
    }
}

Test Steps:

Testdata:

{
  "file": {
    "content": "<?xml version=\"1.0\" encoding=\"utf-8\"?><Types xmlns=\"http://schemas.openxmlformats.org/package/2006/content-types\"><Default Extension=\"aml\" ContentType=\"model/vnd.automationml+xml\" /><Default Extension=\"rels\" ContentType=\"application/vnd.openxmlformats-package.relationships+xml\" /><Default Extension=\"xsd\" ContentType=\"text/xml\" /><Default Extension=\"png\" ContentType=\"image/png\" /><Default Extension=\"bmp\" ContentType=\"image/bmp\" /><Default Extension=\"edz\"ContentType=\"application/octet-stream\" /><Default Extension=\"xml\" ContentType=\"text/xml\" /></Types>",
    "name": "New_Test_Name.xml"
  }
}