diff --git a/4.-Systemtestplan.md b/4.-Systemtestplan.md index 6056c96..a879657 100644 --- a/4.-Systemtestplan.md +++ b/4.-Systemtestplan.md @@ -1,6533 +1 @@ - - - - - - - - - -
- -

        -Table of Contents

- -

1 Scope 

- -

2 Definitions 

- -

3 Test Objects 

- -

4 Features 

- -

5 Test Preparation Strategy 

- -

6 Test Execution Strategy 

- -

7 Test Equipment

- -

8 Test Schedule and Budget

- -

9 Test Planning 

- -

10 Reference/ -Standards 

- -

11 Testcases 

- -

11.1 Test suite <TS-001 File operations>

- -

11.1.1 Testcase -<TC-001-001> (Loading of a valid file with validation)

- -

11.1.2 Testcase -<TC-001-002> (Loading of an invalid file with validation)

- -

11.1.3 Testcase -<TC-001-003> (Export of a valid device to file with validation)

- -

11.1.4 Testcase -<TC-001-004> (Export of an invalid device to file with validation)

- - -

11.2 Test suite <TS-002 GUI> 

- -

11.2.1 Testcase -<TC-002-001> (GUI input field verification)

- -

11.2.2 Testcase -<TC-002-002> (GUI load file via file explorer)

- -

11.2.3 Testcase -<TC-002-003> (GUI Creation and editing of a new device)

- -

11.2.4 Testcase -<TC-002-004> (GUI Export of a loaded device)

- -

 

- -

 

- -
- - -

        -Changelog

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

Version

- 		-

Date

- 		-

Author

- 		-

Comment

-
-

0.1

- 		-

22.04.2022

- 		-

Malte Horst

- 		-

Created

-
- -
- - -

 

- -

1        -Scope

- -

The STP (System Test Plan) describes the -test strategy and test planning.

- -

It contains the tests required to check -whether the requirements specified in the SRS (System Requirements Specification) have been implemented in a functional manner.

- -

The document derived from the STP is the -STR (System Test Report), which additionally specifies the test results.

- -

 

- -

2        -Definitions

- -

AML AutomationML
-TS    Testsuite
-TC    Testcase
-GUI Graphical User Interface
-

- -

 

- -

3        -Test Objects

- -

The following test objects must be verified.

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

Ref.-ID.

- 		-

Product Number

- 		-

Product Name

- 		-

Product Description

-
-

1

- 		-

Build v1.0

- 		-

Standalone Modelling Wizard for Devices GUI

- 		-

Windows standalone application with a GUI

-
- -

 

- -
- - -

 

- -

4        -Features

- -

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.

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

Reg.-ID.

- 		-

Functionality

- 		-

Priority

- 		-

Testsuite ID

-
-

LF10: Import

- 		-

Imports file by absolute path

- 		-

A

- 		-

TS-001

-
-

LF20: File validation

- 		-

Checks whether input file is in a valid format

- 		-

B

- 		-

TS-001

-
-

LF30: Error handling

- 		-

Application throws errors on expected shutdowns and wrong formatting

- 		-

B

- 		-

TS-002

-
-

LF40: GUI

- 		-

Draws GUI for user

- 		-

A

- 		-

TS-002

-
-

LF50: Display device in a readable way

- 		-

Displays loaded device in GUI in a readable way for user

- 		-

A

- 		-

TS-002

-
-

LF60: Edit device

- 		-

Every attribute of devices should be editable

- 		-

A

- 		-

TS-002

-
-

LF70: Create device

- 		-

Creates a new and empty device

- 		-

A

- 		-

TS-002

-
-

LF80: Export device

- 		-

Loaded device is saved as to file

- 		-

A

- 		-

TS-001, TS-002

-
- -

 

- -

5        -Test Preparation Strategy

- -

The creation of tests will be application case based. Two main application cases can be identified, the file operations and the GUI. - -File operations represent the first main application case. Device files need to be loaded, validated and saved to ensure full functionality of the application for the user. - -The GUI is the second main application case. Unlike the previous plugin for the AML Editor, the GUI provides a view of the loaded device with input fields in which the respective device data is displayed. These fields must be checked and features to edit and save device must be validated. -

- -

6        -Test Execution Strategy

- -

Since it is a re-implementation of an already existing software, a complete test is not necessary, but it is still useful. The test should be divided into the following phases: - -1) File operations -2) Graphical User Interface - -Since the file operations are needed for the application to work, these have to be tested first. - -Then the GUI functionality can be tested. This includes the start of the program and the execution of the main features of the application in the GUI. -

- -

7        -Test Equipment

- -

The following equipment must be available -for testing:

- -

•  A computer with Windows 10 or higher

- -

•  The standalone Device Modelling Wizard software

- -

• The “Test Data” folder from the git -repository

- -

 

- -

8        -Test Schedule and Budget

- -

The testing of the application begins as soon as the application is completed. This makes it possible to make the necessary corrections quickly. The conversion library can only be tested once the rules for one input format, but preferably both input formats, have been established. Since only minimal changes are made in the GUI, the GUI can be tested as soon as all adjustments intended for the GUI have been made. - -No budget is needed for the tests, as they are all performed by hand. -

- -

9        -Test Planning

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

Testsuite

- 		-

Test Objective

- 		-

Testplan Creator

- 		-

Testplan Reviewer

- 		-

Tester

-
-

TS-001

- 		-

File operations

- 		-

Linus Eickhoff

- 		-

Florian Kaiser

- 		-

Linus Eickhoff

-
-

TS-002

- 		-

Graphical User Interface

- 		-

Linus Eickhoff

- 		-

Florain Kaiser

- 		-

Linus Eickhoff

-
- -

 

- -

10   -References

- -

[1] SRS TINF20C Device Modelling Wizard

- -

 

- -

11   -Testcases

- -

11.1 -Test suite <TS-001 File operations>

- -

11.1.1  -Testcase <TC-001-001> (Loading of a valid file with validation)

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

Testcase ID

- 		-

TC-001-001

-
-

Testcase - Name

- 		-

Loading of a valid file with validation

-
-

Req.-ID.

- 		-

LF10, LF20, LF30

-
-

Description

- 		-

The test case verifies that it recognizes if a valid file has been loaded.

-

 

-
-

Test Steps

-
-

Step

- 		-

Action

- 		-

Expected Result

-
-

1

- 		-

Open Application.exe from Binary Folder

- 		-

Application starts without probems.

-
-

2

- 		-

Select a valid input file for the validation, by selecting “File” and then “Open” and choose file in explorer

- 		-

The validation is executed successfully, and the conversion is completed correctly without error message.

-
-

3

- 		-

Check if Data was interpreted correctly in “Attributes”, “Generic Information”, “Interfaces”

- 		-

should have all valid data in readable format. P

-
- -

 

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

Test data

- 		-

TD-001-001

-
-

Dataset

- 		-

Vendor Name

- 		-

Device Name

- 		-

ManufacturerURI

- 		-

Device
- Class

- 		-

Product
- Code

- 		-

Validation

-
-

1

- 		-

DHBW

- 		-

Server

- 		-

www.aml.com

- 		-

Computer

- 		-

00256

- 		-

Valid

-
-

2

- 		-

DHBW

- 		-

Server

- 		-

aml

- 		-

Computer

- 		-

00256

- 		-

Fail

-
-

3

- 		-

DHBW

- 		-

Server

- 		-

www.aml.com

- 		-

 

- 		-

00256

- 		-

Fail

-
-

4

- 		-

-

- 		-

-

- 		-

www.aml.com

- 		-

Computer

- 		-

00256

- 		-

Fail

-
-

5

- 		-

-

- 		-

-

- 		-

-

- 		-

-

- 		-

-

- 		-

Fail

-
-

 

-
- -

 

- -
- - -

 

- -

11.1.2  -Testcase <TC-001-002> (Open device, save -changes)

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

Testcase ID

- 		-

TC-001-002

-
-

Testcase - Name

- 		-

Open device, - save changes

-
-

Req.-ID.

- 		-

LF10

-
-

Description

- 		-

This testcase - verifies that a device can be loaded with its data, that the data can be - changed and that it can be saved again.

-

 

-
-

Test Steps

-
-

Step

- 		-

Action

- 		-

Expected Result

-
-

1

- 		-

Select the - “File” dropdown and click on “open”.

- 		-

The explorer - opens, and the file can be chosen.

-
-

 

- 		-

Choose the test - file from TD-001-002 and click “open”

- 		-

“Vendor Name” - and “Device Name” gets filled. The Name of the file will be displayed in the - top right corner.

-

All generic - data, interfaces and attachments will be accessible over their tabs.

-

(If the - Modelling Wizard can not read the file an error message will be shown, and no - file will be opened.)

-
-

 

- 		-

Fill the red - marked entries with data from TD-001-002.

- 		-

Data is overwritten.

-
-

 

- 		-

Click on a free - spot on the GUI

- 		-

The current - selected field in the table gets deselected (and the value is saved)

-
-

 

- 		-

Select the - “File” dropdown and click on “save”.

- 		-

A dropdown of - the explorer opens, and the name of the file can be chosen.

-
-

 

- 		-

Enter a name - and click “save”.

- 		-

A popup opens - and informs about the correct creation and the path of the file.

-

If the name - already the explorer will ask for confirmation of the saving.

-
-

 

- 		-

Confirm the - message.

- 		-

The popup - closes.

-
-

 

- 		-

Open the file - in AutomationML and verify that all data is saved.

- 		-

The file gets - opened and under Attributes all data can be found.

-
-

 

-
- -

 

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

Test data

- 		-

TD-001-002

-
-

Data set

- 		-

File

- 		-

Manufacturer
- URI

- 		-

Device
- Class

- 		-

Product
- Code

- 		-

Validation

-
-

1

- 		-

DHBW_Testfile_01.amlx

- 		-

www.dhbw.com

- 		-

Computer

- 		-

000665000

- 		-

Valid

-
-

2

- 		-

DHBW_Testfile_02.amlx

- 		-

DHBW.png

- 		-

-

- 		-

(no change)

- 		-

Fail

-
-

3

- 		-

Corrupt_Testfile_01_Wrong_Structure.amlx

- 		-

(no change)

- 		-

(no change)

- 		-

(no change)

- 		-

Valid

-

(pop up – - cannot read file)

-
-

4

- 		-

Foreign_Testfile_01_Balluff-BNI_PNT-508-105-Z015-CAEX3-20201022.amlx

- 		-

(no change)

- 		-

(no change)

- 		-

(no change)

- 		-

Valid

-
-

 

-
- -
- - -

 

- -

11.1.3  -Testcase <TC-001-003> (Load standard -libraries)

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

Testcase ID

- 		-

TC-001-003

-
-

Testcase - Name

- 		-

Load standard - libraries

-
-

Req.-ID.

- 		-

LF10

-
-

Description

- 		-

This testcase - verifies that the standard libraries can be loaded into the Modelling Wizard.

-

 

-
-

Test Steps

-
-

Step

- 		-

Action

- 		-

Expected Result

-
-

1

- 		-

Select the - “Standard Libraries” dropdown in the top navbar.

- 		-

A dropdown of - the libraries opens, and one can be chosen.

-
-

 

- 		-

Choose one - library that is not already loaded.

- 		-

The library - will be loaded and can be found on the right sight under “Role Class Library” - or “Interface Class Library”

-
-

 

-
- -

 

- -

11.2 -Test suite <TS-002 Generic data>

- -

11.2.1  -Testcase <TC-002-001> (Create device with -attributes)

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

Testcase ID

- 		-

TC-002-001

-
-

Testcase - Name

- 		-

Create device - with attributes

-
-

Req.-ID.

- 		-

LF20

-
-

Description

- 		-

This testcase - verifies that a device with data in the attributes and the header of “Generic - Data” can be created and saved.

-
-

Test Steps

-
-

Step

- 		-

Action

- 		-

Expected Result

-
-

1

- 		-

Select the - “File” dropdown and click on “new”.

- 		-

A new empty Modelling - Wizard window opens.

-
-

2

- 		-

Fill “Vendors - Name” and “Device Name” in the top navbar, with data from TD-002-001.

- 		-

Data is - entered.

-
-

 

- 		-

Fill the entries - with data from TD-002-001

- 		-

Data is - entered.

-
-

 

- 		-

Click on - “Header” besides “Attributes”

- 		-

The “Header” - table opens

-
-

 

- 		-

Fill the - entries with data from TD-002-001

- 		-

Data is entered

-
-

 

- 		-

Click on a free - spot on the GUI

- 		-

The current - selected field in the table gets deselected (and the value is saved)

-
-

 

- 		-

Select the “File” - dropdown and click on “save”.

- 		-

A dropdown of - the explorer opens, and the name of the file can be chosen.

-
-

 

- 		-

Enter a name - and click “save”.

- 		-

A popup opens - and informs about the correct creation and the path of the file.

-

If the name - already the explorer will ask for confirmation of the saving.

-
-

 

- 		-

Confirm the - message.

- 		-

The popup - closes.

-
-

 

- 		-

Open the file - in AutomationML and verify that all data is saved.

- 		-

The file gets - opened and under Attributes all data can be found.

-
-

 

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

Test data

- 		-

TD-002-001

-
-

Dataset

- 		-

 

- 		-

Vendor Name

- 		-

Device Name

- 		-

ManufacturerURI

- 		-

Device
- Class

- 		-

Product
- Code

- 		-

Temperature

-

Min

- 		-

Temperature

-

Max

- 		-

City

- 		-

Website

- 		-

(Header)

-

Copyright

- 		-

(Header)
- ID

- 		-

Validation

-
-

1

- 		-

Values

- 		-

DHBW

- 		-

Server

- 		-

www.aml.com

- 		-

Computer

- 		-

00256

- 		-

15

- 		-

45

- 		-

Berlin

- 		-

ML.com

- 		-

MIT license

-

         

- 		-

ID-001

- 		-

Valid

-
-

Default

- 		-

-

- 		-

-

- 		-

-

- 		-

-

- 		-

-

- 		-

20

- 		-

40

- 		-

 

- 		-

 

-
-

Units

- 		-

-

- 		-

-

- 		-

-

- 		-

-

- 		-

-

- 		-

Degree

- 		-

Degree

- 		-

Names

- 		-

Urls

-
-

2

- 		-

Values

- 		-

DHBW

- 		-

Server

- 		-

www.aml.com

- 		-

Computer

- 		-

00256

- 		-

15

- 		-

45

- 		-

Berlin

- 		-

ML.com

- 		-

MIT license

- 		-

ID-002

- 		-

Valid

-
-

Default

- 		-

-

- 		-

-

- 		-

-

- 		-

-

- 		-

-

- 		-

20

- 		-

40

- 		-

default

- 		-

default

-
-

Units

- 		-

-

- 		-

-

- 		-

-

- 		-

-

- 		-

-

- 		-

Degree

- 		-

Degree

- 		-

Names

- 		-

Urls

-
-

 

-
- -

 

- -
- -
- - -
- -

11.2.2  -Testcase <TC-002-002> (Create device with -role classes)

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

Testcase ID

- 		-

TC-002-002

-
-

Testcase - Name

- 		-

Create device - with role classes

-
-

Req.-ID.

- 		-

LF20

-
-

Description

- 		-

This testcase - verifies that a device with loaded classes from “Role Class Library” can be - created and saved.

-
-

Test Steps

-
-

Step

- 		-

Action

- 		-

Expected Result

-
-

1

- 		-

Select the - “File” dropdown and click on “new”.

- 		-

A new empty - Modelling Wizard window opens.

-
-

2

- 		-

Fill “Vendors - Name” and “Device Name” in the top navbar, with data from TD-002-002.

- 		-

Data is - entered.

-
-

 

- 		-

Fill the red - marked entries in the “Attributes” table at the bottom of the screen with - data from TD-002-002.

- 		-

Data is - entered.

-
-

 

- 		-

Click on the - library “Library Name” (Data from TD-002-001) on the right side under “Role - Class Library”

- 		-

The entry gets - highlighted.

-
-

 

- 		-

Drag and drop - the library onto the “Generic Information” table.

- 		-

The library - gets added at the last position.

-
-

 

- 		-

Click on the - library in the “Generic Information” table.

- 		-

The entry gets - highlighted. A label with the entry name appears underneath the table.

-
-

 

- 		-

Click on the - new label.

- 		-

The label gets - highlighted.

-
-

 

- 		-

Double click on - the label.

- 		-

Underneath the - label the “Attributes” table opens.

-

If the class - consists of sub classes, these are displayed as indented labels.

-
-

 

- 		-

Fill the - entries with data from TD-002-002

- 		-

Data is - entered.

-
-

 

- 		-

Click on the - label of the subclass.

- 		-

The label gets highlighted.

-
-

 

- 		-

Double click on - the subclass.

- 		-

Underneath the - label the “Attributes” table for the specific subclass opens.

-
-

 

- 		-

Fill the - entries with data from TD-002-002

- 		-

Data is entered

-
-

 

- 		-

Click on a free - spot on the GUI

- 		-

The current - selected field in the table gets deselected (and the value is saved)

-
-

 

- 		-

Select the - “File” dropdown and click on “save”.

- 		-

A dropdown of - the explorer opens, and the name of the file can be chosen.

-
-

 

- 		-

Enter a name - and click “save”.

- 		-

A popup opens - and informs about the correct creation and the path of the file.

-

If the name - already the explorer will ask for confirmation of the saving.

-
-

 

- 		-

Confirm the - message.

- 		-

The popup - closes.

-
-

 

- 		-

Open the file - in AutomationML and verify that all data is saved.

- 		-

The file gets - opened and under Attributes all data can be found.

-
-

 

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

Test data

- 		-

TD-002-002

-
-

Data set

- 		-

 

- 		-

Vendor Name

- 		-

Device Name

- 		-

ManufacturerURI

- 		-

Device
- Class

- 		-

Product
- Code

- 		-

Library Name

- 		-

Spec Version

- 		-

DocLang

- 		-

refURI

- 		-

MIMEType

- 		-

Version

- 		-

Validation

-
-

1

- 		-

Values

- 		-

DHBW

- 		-

Server

- 		-

www.aml.com

- 		-

Computer

- 		-

00256

- 		-

“AutomationML

-

ComponentBaseRCL”

-

>> - “AdditionalDeviceDescription{Class: External Data}”-

- 		-

1.0.0

- 		-

En

- 		-

001

- 		-

.doc

- 		-

1.0.0

- 		-

Valid

-

 

-
-

Default

- 		-

-

- 		-

 

- 		-

 

- 		-

 

- 		-

 

- 		-

1.0.0

- 		-

En

- 		-

000

- 		-

.docx

- 		-

1.0.0

-
-

Units

- 		-

-

- 		-

 

- 		-

 

- 		-

 

- 		-

 

- 		-

Version numbers

- 		-

Country Code

- 		-

Digits

- 		-

Word

- 		-

Version numbers

-
-

Data set

- 		-

 

- 		-

Vendor Name

- 		-

Device Name

- 		-

ManufacturerURI

- 		-

Device
- Class

- 		-

Product
- Code

- 		-

Library Name

- 		-

refURI

- 		-

MIMEType

- 		-

Validation

-
-

2

- 		-

 

- 		-

DHBW

- 		-

Server

- 		-

www.aml.com

- 		-

Computer

- 		-

00256

- 		-

“AutomationMLComponent

-

StandardRCL”

-

>>

-

“Component Icon

-

{Class: Icon}”

- 		-

001

- 		-

.png

- 		-

Valid

-

 

-
-

 

- 		-

 

- 		-

 

- 		-

 

- 		-

 

- 		-

 

- 		-

000

- 		-

.jpg

-
-

 

- 		-

 

- 		-

 

- 		-

 

- 		-

 

- 		-

 

- 		-

Digits

- 		-

Picture

-
-

 

-
- -
- -
- - -
- -

11.2.3  -Testcase <TC-002-003> (Open device, delete -data)

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

Testcase ID

- 		-

TC-002-003

-
-

Testcase - Name

- 		-

Open device, delete - data

-
-

Req.-ID.

- 		-

LF20

-
-

Description

- 		-

This testcase - verifies that attributes and “Role Class Libraires” can be deleted from a - device.

-
-

Test Steps

-
-

Step

- 		-

Action

- 		-

Expected Result

-
-

1

- 		-

Select the - “File” dropdown and click on “open”.

- 		-

The explorer - opens, and the file can be chosen.

-
-

 

- 		-

Choose the test - file from TD-002-003 and click “open”

- 		-

“Vendor Name” - and “Device Name” gets filled. The Name of the file will be displayed in the - top right corner.

-

All generic - data, interfaces and attachments will be accessible over their tabs.

-
-

 

- 		-

Clear the - attributes listed in “Delete Attributes” (Data from TD-002-003)

- 		-

Data is - overwritten.

-
-

 

- 		-

Repeat the - following two step one time for each entry listed in “Delete Library” (Data - from TD-002-003)

-
-

 

- 		-

Select the library - in the “Generic Information” table, which is listed in “Delete Library” (Data - from TD-002-003)

- 		-

The library - gets selected in the “Generic Information” table

-
-

 

- 		-

Press the - “Delete” button in the top right corner of the table.

- 		-

The library - gets deleted

-
-

 

- 		-

Select the - “File” dropdown and click on “save”.

- 		-

A dropdown of - the explorer opens, and the name of the file can be chosen.

-
-

 

- 		-

Enter a name - and click “save”.

- 		-

A popup opens - and informs about the correct creation and the path of the file.

-

If the name - already the explorer will ask for confirmation of the saving.

-
-

 

- 		-

Confirm the - message.

- 		-

The popup - closes.

-
-

 

- 		-

Open the file - in AutomationML and verify that all data is saved.

- 		-

The file gets - opened and under Attributes all data can be found.

-
-

 

-
- -

 

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

Test data

- 		-

TD-002-003

-
-

Data set

- 		-

File

- 		-

Delete - Attributes

- 		-

Delete - Library

- 		-

Validation

-
-

1

- 		-

DHBW_Testfile_03.amlx

- 		-

OrderCode

- 		-

-

- 		-

Valid

-
-

SerialNumber

- 		-

-

-
-

2

- 		-

DHBW_Testfile_04.amlx

- 		-

-

- 		-

“AutomationML

-

ComponentBaseRCL/

-

AdditionalDeviceDescription”

- 		-

Valid

-
-

-

- 		-

“AutomationMLComponent

-

StandardRCL/Component Icon

-
-

 

-
- -
- - -

 

- -

11.3 -Test suite <TS-003 Interfaces>

- -

11.3.1  -Testcase <TC-003-001> (Create device with -interfaces)

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

Testcase ID

- 		-

TC-003-001

-
-

Testcase - Name

- 		-

Create device - with interfaces

-
-

Req.-ID.

- 		-

LF30

-
-

Description

- 		-

This testcase - verifies that a device with additional interfaces can be created and saved.

-
-

Test Steps

-
-

Step

- 		-

Action

- 		-

Expected Result

-
-

1

- 		-

Select the - “File” dropdown and click on “new”.

- 		-

A new empty - Modelling Wizard window opens.

-
-

2

- 		-

Fill “Vendors - Name” and “Device Name” in the top navbar, with data from TD-003-001.

- 		-

Data is - entered.

-
-

 

- 		-

Fill the red - marked entries in the “Attributes” table at the bottom of the screen with - data from TD-003-001.

- 		-

Data is - entered.

-
-

 

- 		-

Click on the - “Interfaces” tab below the top navbar.

- 		-

The interface - view opens.

-
-

 

- 		-

Click on the - interface “Interface Name” (Data from TD-003-001) on the right side under - “Interface Class Library”

- 		-

The entry gets - highlighted.

-
-

 

- 		-

Drag and drop - the interface onto the “Interfaces” table.

- 		-

The interface - gets added at the last position.

-
-

 

- 		-

Click on the - interface in the “Interfaces” table.

- 		-

The entry gets - highlighted. A label with the entry name appears underneath the table.

-
-

 

- 		-

Click on the - new label.

- 		-

The label gets - highlighted.

-
-

 

- 		-

Double click on - the label.

- 		-

Underneath the - label the “Attributes” table opens.

-
-

 

- 		-

Fill the - entries with data from TD-003-001.

- 		-

Data is - entered.

-
-

 

- 		-

Select the - “File” dropdown and click on “save”.

- 		-

A dropdown of - the explorer opens, and the name of the file can be chosen.

-
-

 

- 		-

Enter a name - and click “save”.

- 		-

A popup opens - and informs about the correct creation and the path of the file.

-

If the name - already the explorer will ask for confirmation of the saving.

-
-

 

- 		-

Confirm the - message.

- 		-

The popup - closes.

-
-

 

- 		-

Open the file - in AutomationML and verify that all data is saved.

- 		-

The file gets - opened and under Attributes all data can be found.

-
-

 

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

Test data

- 		-

TD-003-001

-
-

Data set

- 		-

 

- 		-

Vendor Name

- 		-

Device Name

- 		-

ManufacturerURI

- 		-

Device
- Class

- 		-

Product
- Code

- 		-

Interface Name

- 		-

Direction

- 		-

Validation

-
-

1

- 		-

Values

- 		-

DHBW

- 		-

Server

- 		-

www.aml.com

- 		-

Computer

- 		-

00256

- 		-

“AutomationMLInterfaceClassLib”

-

>>

-

“AutomationMLBaseInterface”

-

>> “

-

Order{Class: AutomationMLBaseInterface}”

- 		-

Top

- 		-

Valid

-
-

Default

- 		-

-

- 		-

 

- 		-

 

- 		-

 

- 		-

 

- 		-

Top

-
-

Units

- 		-

-

- 		-

 

- 		-

 

- 		-

 

- 		-

 

- 		-

Directions

-
-

2

- 		-

Values

- 		-

DHBW

- 		-

Server

- 		-

www.aml.com

- 		-

Computer

- 		-

00256

- 		-

“AutomationMLInterfaceClassLib”

-

>>

-

“AutomationMLBaseInterface”

-

>> “

-

Order{Class: AutomationMLBaseInterface}”

- 		-

 

- 		-

Valid

-
-

Default

- 		-

-

- 		-

 

- 		-

 

- 		-

 

- 		-

 

- 		-

 

-
-

Units

- 		-

-

- 		-

 

- 		-

 

- 		-

 

- 		-

 

- 		-

 

-
-

Dataset

- 		-

 

- 		-

Vendor Name

- 		-

Device Name

- 		-

ManufacturerURI

- 		-

Device
- Class

- 		-

Product
- Code

- 		-

Library Name

- 		-

refURI

- 		-

MIMEType

- 		-

Validation

-
-

3

- 		-

Values

- 		-

DHBW

- 		-

Server

- 		-

www.aml.com

- 		-

Computer

- 		-

00256

- 		-

“AutomationMLComponentBaseICL”

-

>>

-

“2DReference{Class: - ExternalDataReference}”

- 		-

001

- 		-

.png

- 		-

Valid

-
-

Default

- 		-

-

- 		-

 

- 		-

 

- 		-

 

- 		-

 

- 		-

000

- 		-

.jpg

-
-

Units

- 		-

-

- 		-

 

- 		-

 

- 		-

 

- 		-

 

- 		-

digits

- 		-

Picture

-
-

 

-
- -
- -
- - -
- -

11.3.2  -Testcase <TC-003-002> (Open device, delete -interfaces)

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

Testcase ID

- 		-

TC-003-002

-
-

Testcase - Name

- 		-

Open device, - delete interfaces

-
-

Req.-ID.

- 		-

LF30

-
-

Description

- 		-

This testcase - verifies that interfaces can be deleted from a device.

-
-

Test Steps

-
-

Step

- 		-

Action

- 		-

Expected Result

-
-

1

- 		-

Select the - “File” dropdown and click on “open”.

- 		-

The explorer - opens, and the file can be chosen.

-
-

 

- 		-

Choose the test - file from TD-003-002 and click “open”

- 		-

“Vendor Name” - and “Device Name” gets filled. The Name of the file will be displayed in the - top right corner.

-

All generic - data, interfaces and attachments will be accessible over their tabs.

-
-

 

- 		-

Click on the - “Interfaces” tab below the top navbar.

- 		-

The Interfaces - view opens.

-
-

 

- 		-

Repeat the - following two step one time for each entry listed in “Delete Interface” (Data - from TD-003-002)

-
-

 

- 		-

Select the interface - in the “Interfaces” table, which is listed in “Delete Interface” (Data from - TD-003-002)

- 		-

The interface gets - selected in the “Interfaces” table

-
-

 

- 		-

Press the - “Delete” button in the top right corner of the table.

- 		-

The interface - gets deleted

-
-

 

- 		-

Select the - “File” dropdown and click on “save”.

- 		-

A dropdown of - the explorer opens, and the name of the file can be chosen.

-
-

 

- 		-

Enter a name - and click “save”.

- 		-

A popup opens - and informs about the correct creation and the path of the file.

-

If the name - already the explorer will ask for confirmation of the saving.

-
-

 

- 		-

Confirm the - message.

- 		-

The popup - closes.

-
-

 

- 		-

Open the file - in AutomationML and verify that all data is saved.

- 		-

The file gets - opened and under Attributes all data can be found.

-
-

 

-
- -

 

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

Test data

- 		-

TD-003-002

-
-

Data set

- 		-

File

- 		-

Delete - Interface

- 		-

Validation

-
-

1

- 		-

DHBW_Testfile_05.amlx

- 		-

Order

- 		-

Valid

-
-

2DReference

-
-

 

-
- -
- - -

 

- -

11.4 -Test suite <TS-004 Attachments>

- -

11.4.1  -Testcase <TC-004-001> (Create device with attachments)

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

Testcase ID

- 		-

TC-004-001

-
-

Testcase - Name

- 		-

Create device - with attachments

-
-

Req.-ID.

- 		-

LF40

-
-

Description

- 		-

This testcase - verifies that a device with attachments can be created and saved.

-
-

Test Steps

-
-

Step

- 		-

Action

- 		-

Expected Result

-
-

1

- 		-

Select the - “File” dropdown and click on “new”.

- 		-

A new empty - Modelling Wizard window opens.

-
-

2

- 		-

Fill “Vendors - Name” and “Device Name” in the top navbar, with data from TD-004-001.

- 		-

Data is - entered.

-
-

 

- 		-

Fill the red marked - entries in the “Attributes” table at the bottom of the screen with data from - TD-004-001.

- 		-

Data is - entered.

-
-

 

- 		-

Click on the - “Attachments” tab below the top navbar.

- 		-

The attachment - view opens.

-
-

 

- 		-

Click on the - “Add” button in the upper left corner.

- 		-

A dropdown list - opens.

-
-

 

- 		-

Choose the - “Dropdown” (Data from TD-004-001).

- 		-

The name gets - added to the two text fields underneath.

-
-

 

- 		-

Click “Select - File” button

- 		-

An explorer - opens.

-
-

 

- 		-

Search the test - File (Data from TD-004-001) and click open

- 		-

The “Element - Name” and the “File Path” in the “Attachable Information” table get filled - with the test data.

-
-

 

- 		-

Click on the - “Add” button in the upper left corner.

- 		-

A dropdown list - opens.

-
-

 

- 		-

Choose the - “Dropdown2” (Data from TD-004-001).

- 		-

The name gets - added to the two text fields underneath.

-
-

 

- 		-

Paste the “Test - Path” (Data from TD-004-001) into the text field besides the “Add Path” - button

- 		-

The path is - pasted.

-
-

 

- 		-

Click “Add Path” - button

- 		-

The “Element - Name” and the “File Path” in the “Attachable Information” table get filled with - the test data.

-
-

 

- 		-

Select the - “File” dropdown and click on “save”.

- 		-

A dropdown of - the explorer opens, and the name of the file can be chosen.

-
-

 

- 		-

Enter a name - and click “save”.

- 		-

A popup opens - and informs about the correct creation and the path of the file.

-

If the name - already exists the explorer will ask for confirmation of the saving.

-
-

 

- 		-

Confirm the - message.

- 		-

The popup - closes.

-
-

 

- 		-

Open the file - in AutomationML and verify that all data is saved.

- 		-

The file gets - opened and under Attributes all data can be found.

-
-

 

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

Test data

- 		-

TD-004-001

-
-

Data set

- 		-

 

- 		-

Vendor Name

- 		-

Device Name

- 		-

ManufacturerURI

- 		-

Device
- Class

- 		-

Product
- Code

- 		-

Dropdown

- 		-

Test File

- 		-

Dropdown2

- 		-

Test Path

- 		-

Validation

-
-

1

- 		-

Values

- 		-

DHBW

- 		-

Server

- 		-

www.aml.com

- 		-

Computer

- 		-

00256

- 		-

Certificate

- 		-

Manual.pdf

- 		-

-

- 		-

-

- 		-

Valid

-
-

Default

- 		-

-

- 		-

 

- 		-

 

- 		-

 

- 		-

 

-
-

Units

- 		-

-

- 		-

 

- 		-

 

- 		-

 

- 		-

 

-
-

2

- 		-

Values

- 		-

DHBW

- 		-

Server

- 		-

www.aml.com

- 		-

Computer

- 		-

00256

- 		-

Component

-

Icon

- 		-

DHBW.png

- 		-

Component

-

Picture

- 		-

“https://upload.wikimedia.org/wikipedia/de/thumb/1/1d/DHBW-Logo.svg/2000px-DHBW-Logo.svg.png”

- 		-

Valid

-
-

Default

- 		-

-

- 		-

 

- 		-

 

- 		-

 

- 		-

 

-
-

Units

- 		-

-

- 		-

 

- 		-

 

- 		-

 

- 		-

 

-
-

3

- 		-

Values

- 		-

DHBW

- 		-

Server

- 		-

www.aml.com

- 		-

Computer

- 		-

00256

- 		-

 

- 		-

-

- 		-

ShortGuide

- 		-

“https://docplayer.net/19663746-C-to-c-a-somewhat-short-guide.html”

- 		-

Valid

-
-

Default

- 		-

-

- 		-

 

- 		-

 

- 		-

 

- 		-

 

-
-

Units

- 		-

-

- 		-

 

- 		-

 

- 		-

 

- 		-

 

-
-

 

-
- -
- -
- - -
- -

11.4.2  -Testcase <TC-004-002> (Open device, delete -Attachments)

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

Testcase ID

- 		-

TC-004-002

-
-

Testcase - Name

- 		-

Open device, - delete interfaces

-
-

Req.-ID.

- 		-

LF40

-
-

Description

- 		-

This testcase - verifies that interfaces can be deleted from a device.

-
-

Test Steps

-
-

Step

- 		-

Action

- 		-

Expected Result

-
-

1

- 		-

Select the - “File” dropdown and click on “open”.

- 		-

The explorer - opens, and the file can be chosen.

-
-

 

- 		-

Choose the test - file from TD-004-002 and click “open”

- 		-

“Vendor Name” - and “Device Name” gets filled. The Name of the file will be displayed in the - top right corner.

-

All generic - data, interfaces and attachments will be accessible over their tabs.

-
-

 

- 		-

Click on the “Attachments” - tab below the top navbar.

- 		-

The attachment view - opens.

-
-

 

- 		-

Repeat the - following two step one time for each entry listed in “Delete Attachments” - (Data from TD-004-002)

-
-

 

- 		-

Select the - interface in the “Attachables Information” table, which is listed in “Delete Attachments” - (Data from TD-004-002)

- 		-

The interface - gets selected in the “Attachables Information” table

-
-

 

- 		-

Press the - “Delete” button in the top right corner of the table.

- 		-

The attachment - gets deleted

-
-

 

- 		-

Select the - “File” dropdown and click on “save”.

- 		-

A dropdown of - the explorer opens, and the name of the file can be chosen.

-
-

 

- 		-

Enter a name - and click “save”.

- 		-

A popup opens - and informs about the correct creation and the path of the file.

-

If the name - already the explorer will ask for confirmation of the saving.

-
-

 

- 		-

Confirm the - message.

- 		-

The popup - closes.

-
-

 

- 		-

Open the file - in AutomationML and verify that all data is saved.

- 		-

The file gets - opened and under Attributes all data can be found.

-
-

 

-
- -

 

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

Test data

- 		-

TD-004-002

-
-

Data set

- 		-

File

- 		-

Delete Attachment

- 		-

Validation

-
-

1

- 		-

DHBW_Testfile_06.amlx

- 		-

ComponentIcon

- 		-

Valid

-
-

ShortGuide

-
-

 

-
- -

 

- -
- -

Author: Jakob Schmidt

- - - - +Link to STP \ No newline at end of file