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

Review how coverage is achieved #28

Open
tansaku opened this issue Jul 19, 2016 · 0 comments
Open

Review how coverage is achieved #28

tansaku opened this issue Jul 19, 2016 · 0 comments

Comments

@tansaku
Copy link
Contributor

tansaku commented Jul 19, 2016

We should review the full process of achieving coverage in this assignment. #27 highlighted a potential shortcoming in the instructions.

I've been concerned for a long time that students are being asked to wrap a lot of code (that they didn't write) in tests. That's great as a legacy activity, but it's not labelled as such, and is potentially confusing in an assignment that's supposed to be about the acceptance unit test cycle - I'd be more comfortable if the tests for all existing functionality were in place and the students were focused on ensuring coverage for the code they were writing themselves?

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

No branches or pull requests

1 participant