- Vinithra S P - CSC India Private Ltd
- Kapil Aggarwal - Springer
- Samanway - Sprinklr
Please visit https://github.com/Bug-Bash/selenium-kiwix for details.
The aims of the Bug Bash extend beyond 'finding bugs', we are keen to encourage and foster collaborative work where we experiment with creating automated test suites for one or more of the kiwix applications. The conference has attracted several hundred passionate individuals; many have significant experience with the Selenium test automation framework. We also have several software testing gurus who are participating in the Bug Bash and available to collaborate with the test automation to enhance the potency of the automated tests.
Participants can work individually and in groups.
Kiwix is an open source offline reader for Web content. It's especially intended to make Wikipedia available offline. It runs on a large range of operating systems, on Android and on the three main Desktop operating systems: Microsoft Windows, Apple Mac OSX and GNU/Linux distributions. Its user interface supports more than 100 languages. Kiwix is used by several schools, universities and libraries all over the world for educational purpose.
More details about testing Kiwix: http://www.kiwix.org/wiki/Testing
To enrich the overall experience, we have invited a few exploratory testing experts to the conference to help the participants of the Bug Bash find interesting bugs and learn some real-world exploratory testing techniques.
We are also pleased to inform you that Julian Harty, our closing keynote speaker and one of the core committers of the Kiwix project, will be present at the conference to guide the team. He, along with the Selenium Core Committee will select the winners.
Suggested approaches include:
- Implementing automated tests for one or more of the kiwix applications, incluing the kiwix web server (called kiwix-serve). These tests can be written using the framework of your choice. For instance here are some possible frameworks for the Android app: Appium, Selendroid, Calabash, Robotium, etc. For the web app, how about Selenium (given the title of the conference :) )
- Reviewing and enhancing current open bugs from the sourceforge project http://sourceforge.net/p/kiwix/bugs/ so they are easier to understand and fix
- Providing translations, especially for incompletely translated locales http://sourceforge.net/p/kiwix/kiwix/ci/master/tree/android/res/
What would we like you to do?
- If you want to work on automating tests: Fork this repository, work on your copy of the respository, and send us pull requests when you've got something to share.
- Bonus points: online CI, for instance travis-ci.org integrates well with github projects.
- If you want to report bugs, feature requests, quirks, etc. file them here https://github.com/Bug-Bash/selenium-kiwix/issues Before you file please check for known (reported) bugs, read the discussions, etc.
We could select:
- top 3 participants with the best test automation suite
- we would also acknowledge the participants who have identified top 10 bugs (if any) in Kiwix.
- Interested participants (teams/individuals) should register on this site to participate in the bug bash competition.
- Julian would kick off the bug bash on Sep 5th at 10:15 AM (right after Simon's opening keynote)
- Team can request help as per their needs from exploratory test experts and few core Se Committee members. Also teams could use the cloud infrastructure from BrowserStack and SauceLabs to setup and run their tests.
- Teams have time till Sep 6th 11 AM to submit their test suite and bug reports. Please submit the link to your github repo where you have all the test suite. Integrating your tests with a CI server is an added advantage. For the bug reports, you are expected to share the links to actual accepted bug reports filed on Kiwix project site. (As the teams work, the Kiwix team will be reviewing and accepting bugs. If need be, they will also be happy to accept fixes.)
- The panel will start their review of the test suite and bug reports at 11:00 AM on Sep 6th.
- Right after Julian's closing keynote, the panel will announce the winners.