Load Testing with Visual Studio Team Service

August 27, 2018 0

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.

Suggested Best Practices for Gherkin

August 16, 2018 0

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.

Unit Testing in C# using XUnit

July 31, 2018 0

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.

Testing Microservices with REST Assured

July 17, 2018 0

Testing and validating REST services in Java is harder than in dynamic languages such as Ruby and Groovy. REST Assured is an open source software testing tool that brings the simplicity of using these languages into the Java domain.

Building a Customer Quality Dashboard

July 10, 2018 0

Software testing metrics can be very difficult: there are thousands of them out there, it is hard to know which ones are important, many are hard to collect, its often difficult to extract meaning from the metrics, and everyone has an opinion on the usefulness of any metric that you might choose. So, what is one person to do?

A Coach Guide to Agile Testing

July 2, 2018 1

A Coach’s Guide to Agile Testing is part of the nice series proposed to Agile coaches by Samantha Laing and Karen Greaves. This book provides a complete plan to run a workshop where members of a Scrum team can understand and learn the concepts behind Agile Testing.

TDD: Red, Green and What?

June 28, 2018 0

The “refactor” step in Test-Driven Development (TDD) is deceptively simple: you just have to improve the code, without changing what it does, right? And the experts make it look so easy: “Look”, they say, “here’s some duplication, which I will remove by “insert magic incantation here”. But how should you decide which “duplication” to remove first? What happens if you fix the “wrong” smell? And how do you even see that duplication in the first place?

1 68 69 70 71 72 171