Update Cassini Test Technique.md #265
Open
Conversation
This file contains hidden or 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
1 participant
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.
Line 13: "I would start a test, Cassini would start and eventually we got Cassini to start literally in seconds, in fact in milliseconds because we trimmed everything so we would just start the application with no state. Then we would start to modify the configuration values, because we exposed the configuration properties as much as our reference, and then I would just go to the view and see what was there.
I am not sure I have understood, or reflected your meaning in this line, especially the phrase "because we exposed the configuration properties as much as our reference,". If you would clarify when you get a chance I will amend the text.