add conceptual content for building test cases/plans at testing/test-cases

[charleszipp]

This is for the new proposed outline in #53

This content should provide guidance on how to build test cases to assert acceptance is met for a given story. Guidance should include but not limited to

• Avoiding false positives with positive and negative test cases
• test case structure (pre-conditions, actions, assertions/verification)
• guidance on organizing/grouping test cases into test plans (i.e. full regression, smoke test, functional area regression)

This article should also provide justification for why test case development is important. For example, test cases become a living documentation of how to test areas of the system and can be easily handed over to the customer after the engagement.

Defining this content is important as its foundational to automated testing. Automation should be a reflection of the concepts defined in this article.

[TessFerrandez]

Just going through some older tickets - looking at the testing content this issue looks resolved now - can you confirm @charleszipp

[charleszipp]

@TessFerrandez the testing content has definitely grown tremendously since this was first opened. However, I am not finding any content that provides guideance on how to develop test cases and organizing those into test plans. I would consider this foundational and the first step before choosing what strategy (e2e, integration, unit, etc) to automate the execution of those test cases/plans. For that reason I would still consider this an open issue.

The automated tests are only as good as the test cases/plans on which they are based.