Component 602328Jump to navigation Jump to search
Use cases to be tested are formulated as playbooks containing Gherkin features on SMW pages
Here are the playbooks and use cases that are currently formulated on SMWCindyKate:
Type "Test Script/Use Case/Manual/Action"
Each use case specifies two types of scenarios:
The server hosting the SMW to be tested is provisioned with a testing environment
The workstation controlling the testing is provisioned with SMW-Browser-Testing
A profile.yml file is created managing the interaction with target servers/SWMs. Here's a sample:
--- <your_label>: mwscriptpath: http://localhost/w/ mwscriptpathtopage: http://localhost/w/index.php?title= mwarticlepath: http://localhost/wiki/ standard_username: sherman standard_password: playbooks_smwurl: http://172.16.0.3/main playbooks_smwapi: http://172.16.0.3/m/api.php gherkin_section_name: Feature
The playbooks are then run like this:
PROFILE=fds PLAYBOOKS='Component 291015' TAGS='--tags @main' ./run.sh
Testing environment/system setup aspects
For the sake of developing tests and not interacting with a target production SMW but rather a recent clone of it, it makes sense to run the entire testing system in a virtualized environment.
Hence, here are some use cases involved with using VirtualBox for this purpose.