|cdd2f191||2020-06-27 22:36:47||Albert Mietus < albert AT mietus DOT nl >||asis|
|f99c30a7||2020-06-27 22:36:40||Albert Mietus < albert AT mietus DOT nl >||RTF support|
|9c7f5c99||2018-11-19 07:18:23||Albert Mietus < albert AT mietus DOT nl >||Updated documentation (analyse of 'run ATSes')|
|21cb4409||2018-11-12 06:11:47||Albert Mietus < albert AT mietus DOT nl >||Anayse of run_ATS/autorun/pw into sequence diagrams|
|3e164d35||2018-11-12 02:40:56||Albert Mietus < albert AT mietus DOT nl >||asis|
|297cb290||2018-11-12 02:39:40||Albert Mietus < albert AT mietus DOT nl >||asis|
|7a6b0b52||2018-11-12 01:21:19||Albert Mietus < albert AT mietus DOT nl >||(HG)ingnore png-files in PathwaysFramework/Design/ dir|
|05aea462||2018-11-12 01:17:16||Albert Mietus < albert AT mietus DOT nl >||small textual refactoring|
|fe534714||2018-11-12 01:16:33||Albert Mietus < albert AT mietus DOT nl >||small textual refactoring|
|1f2f5f5b||2018-11-04 23:40:54||Albert Mietus < albert AT mietus DOT nl >||FIXed typo (in import)|
Pathways is a concept and (reference) implementation for automatic verification (or testing) of a product. Especially, during iterative development; like Agile and Scrum. It also fits in a Lean (sw-development) approach.
With this pathways-framework, testers can write short Automated Test Scripts (‘ATS’es); without being a trained programmer. Those test are Lean, and focus on “user acceptance”: Does the product behave as specified/expected.
As the test should be domain (“business”) specific, several layers of abstraction exist. Typically the are added by the development-team; party by the testers and party by programmers. The framework itself has only a few generic one. Some more examples can be found in the documentation; which include a workshop/training. (The slides are free).
An important design guideline for the pathways-framework is the (maintenance) cost of all those ‘ATS’es; that should be minimised. This (almost) implies, the framework itself is advanced: it allows to be extended with plugins; e.g to interface/communicate with the Product Under Test (PUT), (TsT)Bricks and (TsT)Vectors. This make it possible to combine open-source and propriety parts.
An other goal of Pathways is to provide a (free) “play” and “demo” version of this concept. One can use Pathways to learn this concept, but use a own implementation of it. Several of the later exist (all closed, propriety source).
Pathways was conceived after a challenge of a colleague/friend:
Build a simple version of it.So we can play with it. And learn the concept, easily.
For more information, please see the website (under construction), or contact me.
Welcome to OSDN Wiki system. Here is your chamber Wiki space.
Check Wiki Guide (English) to refer syntax and functions.
(auto generated page)
[Permissions] view:all, edit:admins, delete/config:admins