Better separation of User Acceptance, Integration, Regression and UnitTests
---------------------------------------------------------------------------
Key: QI-270
URL: http://issues.ops4j.org/browse/QI-270
Project: Qi4j
Issue Type: Task
Reporter: Niclas Hedhman
Assignee: Niclas Hedhman
Priority: Minor
I think it would make sense to spend some time to separate the tests into the
above categories.
Unit tests - Really test the classes and not whole subsystems. We have very
little of these at the moment. If these breaks, the build stops.
Integration tests - This is what the majority of our tests today are. Testing
of particular features in a full, live environment. If these these breaks, the
build stops.
Regression tests - Tests that are reported from users via JIRA or mailing list.
These tests doesn't stop the build, but prevent releases and has separate
reporting.
User Acceptance tests - UAT should be built somewhat independently from
development, and organized in "Release Version" structures. Any new feature is
coded up as a UAT preferably ahead of implementation. These tests doesn't stop
build, but will prevent release for versions up to the intended release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
