System Testing

We find System Testing invaluable

Unit Testing tests individual units of source code (functions, methods, modules). System Testing complements unit testing by wrapping an entire application in end-to-end tests that verify the customer’s high-level feature requests and the interaction of unit tested code.

System Testing can:

1. Determine when a project is complete according to the customer’s feature requirements (also known as Acceptance Testing)
2. Verify the interaction of Unit Tested code

HASTE – High-level Automated System Test Environment

Haste represents our early thoughts on the topic of System Testing. It’s a Java framework with well structured testing constructs.

Systir – System Testing In Ruby

Systir is our current best thinking on System Testing. Using the flexibility of Ruby’s language structure, Systir allows custom Domain Specific Languages to be constructed specifically for the application under test. Ideally, a DSL allows the customer to write their own Acceptance Tests as an exercise in Story Driven Development. Further, because of Ruby’s powerful external linkage capability, Systir can drive applications under test regardless of technology selection.