Nonfunctional requirements describe aspects of the system that do not map onto a single piece of functionality. Essentially, they're constraints you need to operate within. Allan Kelly details how running performance tests regularly can be the key to nonfunctional requirements, as well as how much value these constraints produce.
In today’s age of tight deadlines and accelerating delivery cycles of software, test automation is surely favorable for the world of functional testing and critical to the success of big software development companies. But its various benefits have led to unrealistic expectations from managers and organizations. This article highlights the role and use of automation in an agile context and the irreplaceable importance of manual testing.
Approaching performance testing with a rigid plan and narrow specialization often leads to testers' missing performance problems or to prolonged performance troubleshooting. By making the process more agile, the efficiency of performance testing increases significantly—and that extra effort usually pays off multi-fold, even before the end of performance testing.
It is Johanna Rothman's belief that security and performance are no longer nonfunctional requirements in modern-day software development. Instead, we must prepare to accommodate security and performance needs in all projects.
Melissa Benua, director of engineering at mParticle, chats with TechWell community manager Owen Gotimer about the importance of whole team quality, how to get started using the test pyramid, and how developers can start writing testable code.
In this interview, Adam Auerbach, vice president and cohead of the DevTestSecOps practice at EPAM Systems, discusses the book The Kitty Hawk Venture, his experiences at STARWEST, and the topics of performance testing and value stream analysis.
In this interview, Amir Rozenberg, director of product management at Perfecto Mobile, says the success of a business depends on taking advantage of web apps that improve and simplify the customer experience, addressing options that will yield a successful implementation.
In this TechWell interview, Andreas Grabner explains why it's best to test throughout the entire development process. He discusses the severe impact small changes can have on performance and scalability, as well as a few key metrics that will surprise software professionals.
Containerizing applications introduces major changes to the way we run those applications. We can now share infrastructure and resources, but this introduces the need to control the way resources are used—from a sanity perspective first and a financial objective second.
Join Gene Gotimer as he showcases open source tools like JMeter and Gatling to measure different types of performance testing. He'll also discuss how Firefox and Chrome can show what the user experience is like in terms of performance.
Once upon a time, in a land far away, application performance was a differentiator in the market. But in today's competitive landscape, having a highly responsive and scalable application is a basic expectation. Performance no longer lives on the fringe of the quality world.
Nonfunctional tests like performance tests are often left until the end of the delivery cycle because they can be expensive in terms of time, resources, and effort. However, performance issues can be difficult to resolve when found late in the software development lifecycle. Apache JMeter is an open source tool designed to load test functional behavior and measure performance. JMeter can be used to develop, manage, and execute load and performance tests while the code is being developed, rather than waiting to do performance testing until just before release. By using it early in your delivery pipeline, you can find and resolve performance issues as soon as they are introduced. Join Bob Foster as he shows how to use JMeter, design test scenarios, parameterize and seed tests, and execute those tests within Jenkins as part of a CI/CD pipeline.