[almighty] Test "classes"

[Michael Kleinhenz]

Hi,

just to start some discussion. I would divide tests for the ui into
three classes:

1. Unit Tests
-> ususal stuff, testing internal wiring and payload code.

2. Functional Tests
-> tests of the ui behaviour, like "when I add a workitem using the
form, does it appear in the listview?". For this tests, I would go for
a full mocking of external services and use something native to keep
dependencies footprint small.

3. Smoke (or E2E) Tests
-> tests the full setup, starts all services, cases go full stack. For
this, we'll need a powerful test framework that can cover full stack.

For responsibility (or location), I'll see 1 and 2 go into the
respective repository. For 3, I'll would see that as a seperate thing,
*maybe* even a seperate repository.

Any thoughts?

-- Michael

-- 
Michael Kleinhenz
Principal Software Engineer

Red Hat Deutschland GmbH
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany

RED HAT | TRIED. TESTED. TRUSTED.
Red Hat GmbH, www.de.redhat.com,
Registered seat: Grasbrunn, Commercial register: Amtsgericht München,
HRB 153243,
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham,
Michael O'Neill