This repository has been archived by the owner on Mar 5, 2018. It is now read-only.
test change processor handling of ints #51
Merged
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
jmtd
force-pushed
the
test-change-processor
branch
from
2604a32
to
8516387
Compare
jmtd
changed the title
Add a test to ensure change processor can handle int values. Add (back) the dummy.py cct module (previously moved out to the base module repository) at the test-private location tests/modules.
jmtd
force-pushed
the
test-change-processor
branch
from
8516387
to
0472d6d
Compare
jmtd
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Add a test to demonstrate the problem fixed in #52
WIP: test still fails, because the base.Dummy module does not exist.
This is because no modules exist in cct source. Tests will therefore
need to: clone a remote module; provide a test module; mock enough
of cct so that it runs. See issue #50.