A couple of interns started work at Avisi recently. Everyone of them is working on an interesting assignment. We will introduce them in the coming weeks on the blog. Today we are featuring Mitchel Kuijpers. Our testing framework is based on Selenium/webdriver and uses SauceLabs for execution. It’s a typical code first solution. Mitchel’s job is to transform it to a behavior driven framework. Continue reading
A very important part of our software development cycle is functional testing. Luckily, functional testing techniques have evolved tremendously since the dark days of old school testing. Back then, testing was done with countless Excel sheets each having multiple tabs that reflected all the individual scenarios. Each tab looked a bit like this:
- Goto web-page: http://myincredibletestproject.com
- Click on the login link
- Enter username: test
- Enter password: secret
- Click login button
- Verify response: “Failed to login. Invalid credentials.”
In our development structure we use an internally developed integration test system, based on Selenium, to test web application user interfaces. It works great. The Selenium tests run against the test environment (usually JBoss, but it can be any application server) and the tests are run periodically by the continuous integration tool, Jenkins. We can even automatically export test results with test steps to Confluence (our wiki) and link the test cases to their specific use cases.
But there was one thing missing: Calculating the code coverage of the integration tests.