Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unit testing nitpicks/example fixes #57

Merged
merged 4 commits into from
Aug 25, 2015
Merged

Conversation

sdzivanovich
Copy link
Contributor

No description provided.

@@ -45,7 +45,7 @@ We can see that there are three steps here, which correspond to some of the step

1. __Preconditions:__ First, we need to generate the preconditions of the test. If you recall from several chapters back, the preconditions are those conditions which must be met before the actual test starts. In this case, the preconditions are that we have two different linked lists, named _a_ and _b_, and that they contain the exact same data, 1 → 2 → 3, all of which are the same data type.

2. __Execution Steps:__ This is what is actually done in the test. In our example, the equality operator is applied between the two linked lists _a_ and _b_, and will return a Boolean value.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Preconditions are typically things that are "actually done" in unit tests as well

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, poor wording on my part. Good fix.

laboon added a commit that referenced this pull request Aug 25, 2015
Unit testing nitpicks/example fixes
@laboon laboon merged commit 45d2582 into laboon:master Aug 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants