Software Testing Blogs: Load Testing, Unit Testing, Functional Testing
This blog post discusses how to apply a Test-driven Development (TDD) approach to non-functional requirements like performance. He proposes examples on how to test performance with time and memory constraints. He suggests that it is possible to extend this approach to performance, scalability, portability, maintainability and even more abstracts requirements like usability, accessibility.
This blog post presents the Q&A of the “Application Testing in the Cloud Made Easy” session of the Oracle Enterprise Management Forum. It presents the last evolutions in Oracle Application Testing Suite which includes Oracle Functional Testing, Oracle Load Testing and Oracle Test Manager.
Continuous delivery is a software development strategy that optimizes the delivery process to get software delivered as quickly as possible. This blog by Eli Weinstock-Herman explains how to integrate the load testing stage in a continuous delivery process. It presents a detail step-by-step process on how to incorporate the load testing scripts into the Jenkins open source continuous integration tool as a new build step in the delivery pipeline. This step will run the load test and capture the results.
Codeception is a Behavior Driven Development (BDD) testing PHP framework. It aims to provide an original way to write acceptance, functional and unit tests. It uses a scenario approach where you declare what you are doing and what results you expect from your tests. The first post introduces the tool and explains how to write tests with Codeception. A second post digs deeper into the code and shows you how Codeception could be used for unit testing.
Rowan Miller shows how to replace a DbContext based data access layer with an in-memory fake for unit testing in this blog post. He builds an interface that represents the context and then builds an in-memory fake of that context for use in our unit tests. He uses an MVC controller but the same approach can be used with any component that needs to interact with an EF based context, including repositories. The key benefits of this approach are stable and robust tests that execute quickly and exercise a single component, making failures easy to isolate.
This blog post provides a detail process on how to create and run unit tests for Google App Engine applications. The author shows how to write the tests using the standard python unittest module and execute them with gaeunit, a web based test runner. He reminds us that it is easier to write unit tests during design rather than afterwards. We should also keep the tests high level so that further detailed modifications will not break the tests. A short video summarizing Google App Engine unit testing is available at the end.
Running stress- or load-tests of asynchronous REST/HTTP services with JMeter is only the first step in performance improvement. If the applications have problems when load increases, you need to find where the issues are. You can spend a lot of time to examine the code base before – if ever – finding the cause of the performance problem. This blog post provides an introduction on how to record and examine telemetry performance measurements with Yourkit3 after running JMeter tests.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates