Feature List

Twister available features ( click for details ):

---

• Username/Password access
• User configurable
• Configurable email list
• Flexible database schema ; it is user defined and configured in Twister using an XML file
• [Plugins mechanism](https://github.com/Luxoft/Twister/wiki/Plugins mechanism) - Twister can load customized plugins; Here are details about [how to create a plugin] (https://github.com/Luxoft/Twister/wiki/Plugin-development)
• [Test bed details](https://github.com/Luxoft/Twister/wiki/Test bed details) can be defined using GUI
• multitenancy execution
• define group of tests as suites
• define the groups of tests using simple operation drag&drop
• define a file as been pre-requisite ( could be an init script or a script that is mandatory for the rest of the scripts within that suite )
• multiple suites can be defined; every suite can target a separate test bed
• a suite can be defined inside another suite
• edit the test cases using an embedded editor with syntax highlight or using an external editor. The external editor is user defined
• the test cases can contain sections to define the title and the description
• live monitoring of the execution
• control execution status ( start/pause/resume/stop execution )
• display in real time the CLI ouput, summary information with the results and debug information
• possibility to search through the logs
• possibility to save the output logs locally
• user can mark some scripts to be skipped
• reporting system
• distributed execution; execution of a single central engine instance and multiple instances for execution processes
• can execute Pythyon/TCL/Perl scripts
• support for record and play tools Sikuli, Selenium and TestComplete
• can be started/controlled from command line ( for batch execution )
• results recorded in database
• read and pass parameters to a test for execution
• uses XML-RPC to communicate with GUI so the GUI can be completely changed
• SVN plugin available in GUI
• central engine REST interface for viewing logs and stats
• mechanism to retrieve information from an external script to use it when the results are saved in database ( e.g. get a build version from a device and use it when the testing results are recorded in database ).
• stop on fail - if a test file fails, and the file is mandatory, and the "stop on fail" flag is activated, the execution process stops. The files that are optional must not stop the execution process if they fail. The "stop on fail" flag can be easily activated and deactivated.
• run temporary - a mechanism that allows 1 or more files to be run several times, without losing the stats from last run and without saving to database or sending e-mail report.