| [cosmos-dev] COSMOS M2 QA tasks - unit versus E2E/integration testing and who does what |
Shivvy,
This is in reference to your note on you researching the unit test cases. Please note that in the COSMOS call this past Tuesday, it was agreed that in i8, the COSMOS developers will continue to do the unit tests.
The QA crew will be responsible for two things:
1. Tracking that the developers complete ALL the unit tests for the ERs they complete. Mark also talked about a process upgrade which would prevent an ER from being closed until each developer completes their respective unit tests. In other words, QA does NOT complete the unit tests for each ER….
2. The QA staff owns the E2E/integration tests as in i7, i.e. they execute / track / manage the E2E fully.
Thus, the scope of the QA team activities from an actual testing perspective is fairly limited. If you wish to extend / change the scope of ANY of these items (i.e. unit OR E2E/integration tests), please bring this up in the next COSMOS meeting along with your recommendations.
Please note that I have NO preferences either way; this is simply a statement of the current state; you are free to change it in any direction you desire; provided the COSMOS team is consulted.
Also, please note that the E2E/integration tests do NOT do any sort of unit coverage in anyway, i.e. the two types of tests are totally orthogonal to each other.
Thanks,
Jimmy Mohsin
Cell +1-609-635-1703