Tutorials and resources on how to apply test automation in software testing
What might seem obvious to some people could be weird to other. This is still the case for applying unit testing to JavaScript code in multiple browsers. In his blog post “Learning How to Set Up Automated, Cross-browser JavaScript Unit Testing”, Philip Walton provides a step-by-step approach process to create some automated testing of your JavaScript code.
Testing has been part of the software delivery lifecycle since… forever. Now, Agile methodologies make testing part of everyone’s responsibilities. But despite this, despite big steps forward with TDD, BDD, and other approaches which bring automated testing to the forefront of the development process, many developers still behave as if testing is a second class citizen. What can you do to help developers a) write tests b) write meaningful tests and c) write readable tests?
SpecFlow is an open source Behavior-Driven Development (BDD) tool for .NET. SpecFlow uses the official Gherkin parser and supports the .NET framework, Xamarin and Mono. You can use SpecFlow to define, manage and automatically execute human-readable acceptance tests in .NET projects. Writing easily understandable tests is a cornerstone of the BDD paradigm and also helps build up a living documentation of your system. Anton Angelov has created a series of articles dedicated to Specflow that starts with an introduction tutorial.
For software developers, the Code Review process has been essential for ages, but they can also be used in software testing when you create test automation code.
Mockito is a popular and powerful open source Java mocking framework. In order to achieve good unit tests, you need to make use of mocks and stubs. And that’s exactly what this talk will be about: What is a mock?
Testing the graphical user interface (GUI) is one of the most important task of the functional testing phase, as its quality will often greatly influence the customer opinion of your application. In this article, Denis Markovtsev discusses the different types of GUI testing and presents the best practices to automate this activity.
Most research on Agile Testing and QA have requirements on highly automated testing/CI and an Agile or Scrum project-management structure. How can we iterate towards a more Agile testing process, with all the benefits that entails, when some of the common requirements are missing or undesirable in the near-term?
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates