Overview, reorganize into micro and macro phases #7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The high-level overview page makes some really nice distinctions between the different phases of a test.
However, the first section mentions the
planning->scripting->executing->analysiscycle, then it shifts to the snowball of motivations, then shifts backs to planning.So, I split what I perceived as the more long-term motivations into their own section at the end. I'm not sure if this organization is logical, so I'm asking for a check.
If there is a better way to organize the info, great! I just got confused about what an instance of the word "phases" meant, then ended up doing a whole section of surgery :-)