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

Needs CI and Unit Testing #32

Open
jblakeman opened this issue May 21, 2016 · 0 comments
Open

Needs CI and Unit Testing #32

jblakeman opened this issue May 21, 2016 · 0 comments
Assignees
@jblakeman
Labels
enhancement

Comments

@jblakeman
Copy link
Owner

jblakeman commented May 21, 2016 •
edited
Loading

We should add integration tests for all primary success cases, mocking socket connections (latency testing), Launchpad mirror page responses (status, bandwidth, info tests), stdin for user interaction, /etc/apt/sources.list reads and successful file generation (builtins.open).
@jblakeman jblakeman self-assigned this May 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jblakeman jblakeman

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jblakeman