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

Proposal: Developing a Selenium Based GUI Automated Tests #3380

Closed
GalaDe opened this issue Feb 16, 2017 · 5 comments
Closed

Proposal: Developing a Selenium Based GUI Automated Tests #3380

GalaDe opened this issue Feb 16, 2017 · 5 comments

Comments

@GalaDe
Copy link

GalaDe commented Feb 16, 2017

This technique will help to reduce the effort required in GUI modeling and test coverage analysis during the software testing process. With automated testing, a tester or the developer can use a testing framework such as Visual Studio, ReSharper and Selenium Web Driver to finish all of the usual test cases and print out a test result file without having to manually execute the tests themselves. This allows the tester to leave the workstation running the tests on its own while working on another task simultaneously. I believe having these automated tests will greatly increase productivity at Exercism for both developers and testers.

Effective Automation:

  1. Reduced utilization of manual resources
  2. Reduced test cycle time
  3. Improved test coverage, since testing may be done more frequently.

In my opinion, automated testing will be a huge boon to an Exercism as it allows developers to run the test suite right after the implementation of a new feature. It will provide additional guaranteed test coverage without the risk of human error. The tests will cover all the main functionality of the UI.

I will glad to develop the automated tests, if you don't have them.

@kytrinyx
Copy link
Member

@GalaDe Thank you so much for offering. I completely agree that having a good suite of GUI tests would be useful for all of the reasons that you mention.

The one concern that I have at the moment is that the current website is a prototype and we're in the process of doing from-the-ground-up / from-scratch research and user experience design. This means that we expect to completely re-imagine the user interface.

I would not want to have you put in a huge amount of effort towards these tests right before the user interface completely changes.

/cc @exercism/reboot

@kytrinyx
Copy link
Member

For more about the design work that we're undertaking (and the reasons for it) see:

@GalaDe
Copy link
Author

GalaDe commented Feb 21, 2017

Hi @kytrinyx, Thank you for your response. I agree, it doesn't make any sense to develop automated tests, if you're planning to change the GUI. I will be happy to help you in the future with that.

@kytrinyx
Copy link
Member

@GalaDe Awesome! I am making a note of this. I'm going to close this, and we'll open a new issue (and ping you in it) when we're ready to add GUI tests.

@GalaDe
Copy link
Author

GalaDe commented Feb 21, 2017

@kytrinyx, sound good!

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