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.

Sign up for GitHub

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

Jump to bottom

write UI tests or whatever it is that they call it for this kind of thing #66

Open
audreyseo opened this issue Dec 31, 2016 · 0 comments
Open

write UI tests or whatever it is that they call it for this kind of thing #66

audreyseo opened this issue Dec 31, 2016 · 0 comments
Assignees
@audreyseo
Labels
dream goals testing

Comments

@audreyseo
Copy link
Owner

audreyseo commented Dec 31, 2016 •
edited

I need to have unit tests for everything, especially the regexes, and just all of the logic, so that I can be sure that this is working 100% of the time.
@audreyseo audreyseo added this to the Initial Deployment milestone Dec 31, 2016
@audreyseo audreyseo self-assigned this Dec 31, 2016
@audreyseo audreyseo removed this from the Initial Deployment milestone Dec 31, 2016
audreyseo added a commit that referenced this issue Jan 19, 2017
@audreyseo
Started looking into unit testing
3e4eedb 
Working on Issue #66 - write unit tests
I really should split this issue into far smaller issues because I
really do not think that it is really feasible or practical for me to
write unit tests for all 10+ classes and have it be under the umbrella
of a single issue. Each class in itself should probably have its own
issue.
Anyway, Swift doesn't seem to have a good mocking framework like
AngularJS does, with Jasmine, but that's probably because of the newness
of Swift and the unpopularity of unit testing among iOS developers,
which I find strange.
It is rather difficult though for me to test the code because I barely
have any functions that take arguments, which is a problem. I also
haven't really structured the code to be friendly for dependency
injection, like I did in Angular, so I'm going to have to write some
workarounds for that.
I'm really not sure either if I should be testing the view controllers
as they are now because the code is a lot of just making alterations to
various instance variables of the view controller...well, I guess I can
do something about that.
@audreyseo audreyseo changed the title write unit tests write UI tests Jun 1, 2017
@audreyseo audreyseo changed the title write UI tests write UI tests or whatever it is that they call it for this kind of thing Jun 1, 2017
@audreyseo audreyseo removed the ready label Jun 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@audreyseo audreyseo

Labels
dream goals testing
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@audreyseo