Main Page

From STIQ

Revision as of 12:58, 18 November 2011 by WikiSysop (Talk | contribs)
(diff) ←Older revision | Current revision (diff) | Newer revision→ (diff)
Jump to: navigation, search

StoryTestIQ (STIQ) is a test framework used to create Automated Acceptance Tests or Story Tests.

STIQ is a mashup of Selenium and FitNesse. It is "wiki-ized" Selenium with widgets and features that make it easier to write and organize Selenium tests.

When developing web applications, it is helpful for a cross-functional team to have a definitive and executable view of the requirements for an iteration. STIQ is used to record Customer needs and acceptance criteria; the tests are a big part of the "Definition of Done". The Story Tests written at the beginning of an iteration will initially fail. It is the responsibility of the team to implement the requirements in order to make the Story Tests pass. This practice is called Story Test Driven Development and it is a natural extension of the well known Test-Driven Development and Automated Acceptance Testing practices.

STIQ may also be used by traditional development teams to create Functional Tests. They may be used to supplement the team's unit tests with a Story Test Driven Development approach or even to automate existing manual test cases.

Check out the Getting Started page. After you've installed STIQ, take a look at the Create A Test page to get going with a very simple test. Then spend some time with the included documentation for more details on how to create suites and test cases.


Why STIQ?

STIQ provides several key advantages over pure Selenium:

  1. In-browser editing of tests, shortening the write/execute cycle.
  2. Test composition, building more complex tests from re-usable test components.
  3. Greatly reduced test maintenance cost and increased design flexibility due to test component re-use.
  4. Test refactoring tools which simplify test maintenance.
  5. Grouping of tests by tags, allowing tests to be executed by feature groups, speed of execution, Sprint in which the test was written (in a Scrum context), or arbitrary other categorizations.
Personal tools
Noteworthy