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

Objective-C tests review #627

Closed
3 tasks
mattheworiordan opened this issue Aug 8, 2017 · 6 comments
Closed
3 tasks

Objective-C tests review #627

mattheworiordan opened this issue Aug 8, 2017 · 6 comments
Assignees
Labels
enhancement New feature or improved functionality.

Comments

@mattheworiordan
Copy link
Member

Our old tests were written in Obj-C and we use the new Swift tests for most of our test coverage now. We should consider whether we can dispose of the old Obj-C tests completely or not by working out:

  • How much of our coverage is provided by Obj-C tests
  • How easy is it to simply get the Obj-C tests running
  • How easy is it to port the test to Swift
@mattheworiordan mattheworiordan added the enhancement New feature or improved functionality. label Aug 8, 2017
@mattheworiordan
Copy link
Member Author

Thanks @tcard for reviewing this.

@ricardopereira
Copy link
Contributor

@mattheworiordan Will do. Should I then deactivate those legacy tests?

@ricardopereira ricardopereira self-assigned this Aug 11, 2017
@mattheworiordan
Copy link
Member Author

Should I then deactivate those legacy tests?

Yes, I think so personally so that we have a passing CI again. @ricardopereira think you'll have time to look at this?

@ricardopereira
Copy link
Contributor

Yes, maybe tomorrow or wednesday.

@mattheworiordan
Copy link
Member Author

Thanks @ricardopereira

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or improved functionality.
Development

No branches or pull requests

3 participants