Tutorials and resources on how to apply test automation in software testing
Even in the era of cloud computing when you can scale your infrastructure more easily, building and managing a software that can scale and support a large number of users is more than just putting more powerful hardware. In this article, Dmitro Kosenko discusses the main principles behind load testing and proposes a step by step process to perform load testing using Microsoft’s Visual Studio Team Service.
Gherkin is the language that many Behavior-Driven Development open source software testing tools like Cucumber or Behat use to define test cases. Gherkin is designed to be non-technical and human readable, and collectively describes use cases relating to a software system.
Part of the .NET Foundation, xUnit.net is an open source unit testing tool for the .NET Framework (C#, F#, VB.NET, etc). xUnit.net works with ReSharper, CodeRush, TestDriven.NET and Xamarin.
Behavior-Driven Development (BDD) is an Agile approach that mixes requirement gathering, documentation and acceptance testing. You write human-readable sentences describing the features of your application and how they should work. Then you implement this behavior using a tool that produces automated acceptance tests to verify that the feature is implemented correctly. Open source .NET BDD tools like SpecFlow are used to store the requirements as live documentation and to perform functional or acceptance tests.
This tutorial presents how to do Test-Driven Development (TDD) for a Spring Boot application and how some of the latest Spring Boot annotations and utilities make that easy. Ever wonder how to test a hard problem like caching or write an integration test without making an external API call? Or come across a situation where testing something was so hard that it never got tested?
Page-Object pattern is very commonly used during software testing when you use test automation frameworks. However, as the scale of the framework grows, there is a limitation on how much reusability really happens. It can inherently become very difficult to separate the test intent from the business domain. This presentation discusses the issues with the Page-Object pattern and the solution that you can implement – Business Layer – Page – Object pattern, to help your code staying DRY.
It is not easy to write good automated tests as it involves to create and maintain a stable testing environment and configure the right tools. In this free less extracted from his “Test With Spring” course, Petri Kainulainen explains how to run integration tests With Maven, Spock edition.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates