Effective test management is an important element of a software development process. A well-planned and organized test management can ensure that the best possible software is produced within fixed time and resources.
The necessity to develop increasingly sophisticated software solutions has led to comprehensive,
In this post, I am going to show how to create load tests for a REST API application with the help of Gatling 2. This will be a step-by-step guide — starting from integrating Gatling 2 using SBT plugin, creating/configuring test scenarios, and all the way to running the Gatling tests.
The primary purpose of any commercial website is to effectively sale services or products. That is where the user experience design which includes various usability solutions comes into focus. This article considers key concepts of the user experience and usability and answers the basic questions:
Here you can find out how to create integration tests for RESTful service on the example of application shown in the article "Building REST service with Scala". To create the tests, I am going to use spray-testkit DSL, as it provides a simple way to test route logic for services built with spray-routing.
Test cases are the key elements of testing, therefore the ability to write effective tests is one of the most important technical skills of a quality assurance engineer. This post covers conditions to writing efficient test cases, the most preferable naming conventions, and the best practices on structuring and writing the tests.
The modern IT marketplace of the high technologies offers the multiplicity of great solutions for software testing. In this article we review the pros and cons of the most famous web-based test management tools: SpiraTest, TestRail and TestLodge. Every of the mentioned services is the comprehensive web-based test management software that allows to control, monitor and organize effectively the testing efforts of the QA department.
Regression testing is one of the most frequently used objectives of testing. It focuses on the application retesting after changes are implemented. That changes can be local, - like new features or bug-fixes, or global, - like new business logic implementation.