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 test all the things #34

Closed
devgeeks opened this issue Feb 10, 2014 · 6 comments
Closed

Unit test all the things #34

devgeeks opened this issue Feb 10, 2014 · 6 comments
Assignees
Labels
Milestone

Comments

@devgeeks
Copy link
Collaborator

Currently, there are almost NO unit tests.

Since mocking Crypton would be difficult, maybe the unit tests could actually rely on connecting to a real Crypton server?

@devgeeks devgeeks added this to the 1.0 milestone Feb 10, 2014
@devgeeks
Copy link
Collaborator Author

@kenmanheimer - thoughts?

@kenmanheimer
Copy link
Contributor

@devgeeks - apparently the crypton guys use a local server to unit test the crypton client code. I'm going to talk with them about it in the dev call, today.

@devgeeks
Copy link
Collaborator Author

👍

@devgeeks
Copy link
Collaborator Author

Speaking to @ecto, it might be best to functionally test rather than unit test when it comes to Crypton

@devgeeks devgeeks assigned devgeeks and unassigned devgeeks Feb 23, 2014
@devgeeks devgeeks removed this from the Android 1.0 milestone Feb 23, 2014
@devgeeks
Copy link
Collaborator Author

I think the goal of this issue should be to unit test all the bits that AREN'T Crypton dependant using mock data.

  • Models
  • Collections
  • etc

@devgeeks devgeeks added this to the 1.0.0 milestone Jun 26, 2014
@devgeeks devgeeks self-assigned this Jun 26, 2014
@devgeeks devgeeks modified the milestones: 1.0.1, 1.1.0 Sep 3, 2014
@shibacomputer
Copy link
Contributor

Sticking with functional testing for the time being.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants