...
| Gliffy Diagram |
|---|
| size | 600 |
|---|
| displayName | Testbed_Test-Architecture |
|---|
| name | Test |
|---|
| pagePin | 5 |
|---|
|
Generic test cases
The testbed provides a set of generic test cases to be used with every product in the testbed (Testbed supported test cases). These include standard authentication flows which are supported by every IdP/SP product, i.e. they can be used out of the box.
| Gliffy Diagram |
|---|
| size | 600 |
|---|
| displayName | Testbed generic test case sequence diagram |
|---|
| name | Testbed generic test case sequence diagram |
|---|
| pagePin | 4 |
|---|
|
Testbed configuration
The testbed contains a general Selenium configuration that describes the generic test cases. The tests are using a standard flow, which expects a specific page sequence and defined HTML field identifiers (e.g. for username and password). The field identifiers are dynamic and can be replaced by including a products specific configuration file, which is provided by the product maintainer.
Product specific configuration
Every product directory should contain a configuration file that specifies the HTML field identifiers used by the product.
Product specific test cases
Each product may define its own test cases to test specific features. These test cases can be defined using the Behave/Selenium specification of the testbed and added to the product directory. They are then executed if the product is deployed in the testbed.
| Gliffy Diagram |
|---|
| size | 600 |
|---|
| displayName | Testbed specific test case sequence diagram |
|---|
| name | Testbed specific test case sequence diagram |
|---|
| pagePin | 2 |
|---|
|
<<test sequence diagram>>
