Selenium is a widely used open source tool used for software testing that provides a record/playback IDE for authoring software tests without learning a specific test scripting language. In this article, Brian Van Stone provides some best practices on how to successfully use Selenium for your test automation efforts.
It’s commonly said that Test Automation means you need less testers on the team, it speeds up the testing process and allows more time for Exploratory Testing. In this talk Richard shares his critique of these common outcomes by calling upon his experiences of working in and managing teams where Automation has played a crucial part in the testing approach and has been used to great effect; but hasn’t resulted in the above outcomes.
There is always a lot of discussions about the costs and benefits of unit testing. The opposition was exacerbated by the adoption of Test-Driven Development (TDD), a technique that recommends writing unit tests before you write the code. In this blog post, Steven Sanderson discusses unit testing with a costs and benefits perspective.
Software testing is an activity that has often been placed at the end of the software development life cycle, something that you did if there were some time left before the project deadline. In his book ” Scrum Shortcuts without Cutting Corners”, Ilan Goldstein explains that the software testers should be active since the beginning of the project.
Did you ever wonder how testing at Google looks like? What tools we use to help us out and how do we measure and act on test coverage? We will briefly describe the development process at Google, then focus on use of code coverage measurement and how we use code coverage to improve code quality and engineering productivity.