Full list of solved tasks is available at: https://geo2tag.atlassian.net/secure/RapidBoard.jspa?rapidView=21&view=reporting&chart=sprintRetrospective&sprint=171
Next version plan:
The solution of the issue “Periodic drop of the test src/tst_selenium/test_service_list_page.py” (https://geo2tag.atlassian.net/browse/GT-2203) is postponed since this test is not critical.
On 17 December a seminar “Testing web applications with Selenium” was held.
The report has illustrated the main features of the framework and their application to solve real-world tasks in web development.
Based on the experience of using Selenium in the Geo2Tag project the following questions were considered:
- structure of Selenium API
- how to automatize actions in browser
- how to write UI tests for web interfaces
- how to integrate Selenium and frameworks for unit testing
- how to set up continuous integration and fully automate the testing of web applications
The report demonstrated practical examples of tests on Python. For correct work of examples you need installed Python 2.7 with selenium package.
The report is addressed to web developers, web designers and everyone who one way or another faced with the issues of automation of certain actions on web pages.
Speaker: Mark Zaslavskiy, postgraduate student at NRU ITMO, an active member of the Open Source and Linux Laboratory, one of the authors and developers of Geo2Tag project.
Here you can see a slide deck from the seminar: http://www.slideshare.net/osll/testing-with-selenium
Here you can see the video of the report (russian):
Here is the summary about the seminar: https://vk.com/osllru?w=wall-67948418_29
Here you can find the examples: https://bitbucket.org/osll/geo2tag_seminars/raw/c64f6dfdf344b945af40828608ff6717ef346b38/selenium_report_17_12_15/selenium_report.zip
Link to the russian source: http://geo2tag.org/?page_id=1418&lang=ru_RU
Full list of solved tasks is available at: https://geo2tag.atlassian.net/secure/RapidBoard.jspa?rapidView=21&view=reporting&chart=sprintRetrospective&sprint=166
- change state of a plugin using the ‘X’ button on the page /admin/plugin
- jump to the page of plugin configuration using the ‘C’ button on the page /admin/plugin
- fix integration tests:
Next version plan: