No Tags

Frequently used words (click to add to your profile)

javac++androidlinuxc#objective-cqt誰得cocoawindowspythonphprubygameguibathyscaphec翻訳omegat計画中(planning stage)frameworktwittertestdombtronvb.netdirectxarduinopreviewerゲームエンジン



最近のWikiの更新 (Recent Changes)

No changes on this wiki.


サイドバー (Side Bar)


Release Files

No download files.

Recent Commits

Rev.TiempoAutorMensaje RSS
cdd2f1912020-06-27 22:36:47Albert Mietus < albert AT mietus DOT nl >asis
f99c30a72020-06-27 22:36:40Albert Mietus < albert AT mietus DOT nl >RTF support
9c7f5c992018-11-19 07:18:23Albert Mietus < albert AT mietus DOT nl >Updated documentation (analyse of 'run ATSes')
21cb44092018-11-12 06:11:47Albert Mietus < albert AT mietus DOT nl >Anayse of run_ATS/autorun/pw into sequence diagrams
3e164d352018-11-12 02:40:56Albert Mietus < albert AT mietus DOT nl >asis
297cb2902018-11-12 02:39:40Albert Mietus < albert AT mietus DOT nl >asis
7a6b0b522018-11-12 01:21:19Albert Mietus < albert AT mietus DOT nl >(HG)ingnore png-files in PathwaysFramework/Design/ dir
05aea4622018-11-12 01:17:16Albert Mietus < albert AT mietus DOT nl >small textual refactoring
fe5347142018-11-12 01:16:33Albert Mietus < albert AT mietus DOT nl >small textual refactoring
1f2f5f5b2018-11-04 23:40:54Albert 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.

--Albert Mietus

Latest updated Tickets

No tickets

About Chamber Wiki

Welcome to OSDN Wiki system. Here is your chamber Wiki space.

Check Wiki Guide (English) to refer syntax and functions.