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

Manual testing of features after update #200

Closed
cztomczak opened this issue Jan 26, 2016 · 1 comment
Closed

Manual testing of features after update #200

cztomczak opened this issue Jan 26, 2016 · 1 comment
Milestone
v47

Comments

@cztomczak
Copy link
Owner

We still have no automated way of testing. See Issue #59 to add that. Most of the tests are in the wxpython.py example and need to be fired manually. This is tedious work and is error prone.
@cztomczak cztomczak added this to the Chrome 47 milestone Jan 26, 2016
@cztomczak cztomczak changed the title Chrome 47: manual test all features after update Chrome 47: manual testing of all features after update Jan 26, 2016
@cztomczak cztomczak changed the title Chrome 47: manual testing of all features after update Chrome 47: manual testing of features after update Jan 26, 2016
@cztomczak
Copy link
Owner Author

Unit tests added. Also the compile.py script runs all examples automatically. This should be enough for now.

@cztomczak cztomczak modified the milestone: Chrome 50+ Feb 24, 2017
@cztomczak cztomczak changed the title Chrome 47: manual testing of features after update Manual testing of features after update Feb 24, 2017
@cztomczak cztomczak added this to the v47 milestone Feb 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v47
Development

No branches or pull requests
1 participant
@cztomczak