CubicTest lets the "customer" (non-technical / business-side person) as well as developers write automatable tests of a web application.
Tests written in CubicTest can be used
- to report bugs in the form of a failing test
- for regression test existing features during the life cycle of a project
Our experience is that web components are best extensively tested at the Controller / Action level with a unit testing framework (and not with CubicTest), to make them faster to run and avoid starting a web server.
CubicTest is in our experience best used for
- System sanity checks (check all main functions of a web applicatins), i.e. testing web flow and web configuration
- Testing JavaScript (although there are seperate testing frameworks for that too)
- Testing existing/legacy web applications without unit tests at the Controller / Action level
One should try to write the tests as focused as possible, not asserting more than strictly necessary. Manual testing is much better for finding bugs in content.