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

cleanup and improve software updater tests #16

Open
choksi81 opened this issue May 24, 2014 · 2 comments
Open

cleanup and improve software updater tests #16

choksi81 opened this issue May 24, 2014 · 2 comments
Assignees

Comments

@choksi81
Copy link
Contributor

The software updater tests need to be cleaned up, made easier to run, and made possible to automate (at least some of them should be possible to automate on some OSs).

It needs to be clearer when there is an error, as they currently will say success when only parts of the test were successful even though other parts failed, e.g. #531. At a minimum, if it is too difficult to state success with absolute certainty, the output of the tests should make clear that apparent success does not mean actual success and provide, in the output, the information the human running the tests needs in order to determine whether the test was truly successful.

@choksi81 choksi81 self-assigned this May 24, 2014
@choksi81
Copy link
Contributor Author

Author: jsamuel
As they have gone this long without being cleaned up, it seems like it wouldn't be the end of the world to wait until the imminent rewrite of the updater, even if that is at least a few months out.

@choksi81
Copy link
Contributor Author

Author: justinc
I think we should move these tests to utf. This port won't take long and I don't think we're running the tests much because we're using UTF primarily now.

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

2 participants