After the need for healthcare brought down the Obamacare website (www.healthcare.gov), it can be easily stated that performance testing plays a critical role in the software development life cycle (SDLC). Companies cannot afford to put performance testing activities towards the end of their development pipeline. Automated regression testing has slowly been making its way to the head of the class due to agile development best practices. Why does performance testing still hide in the back?
The feature being developed is not ready for performance testing
Even if the feature has not been fully developed, a lot goes into planning and making sure that the right tests are being defined. If development is being tracked with a Kanban board, get in the practice of adding a performance testing story that can be worked on every sprint. With continuous integration becoming a standard practice, try to design the stories so that they become part of your CI process.
The infrastructure is not ready to do load testing
With many cloud services offering solutions for performance testing, such services can be used to execute small load testing tests against the application being developed. In some cases, such services may actually be cheaper than hosting an internal infrastructure to perform the load testing.
There isn't budget for performance testing tools
The open source community has developed mature tools for performance testing. Even enterprise companies have developed free or community edition of their software for performance testing. At this point, the only cost is the time spent by an engineer to learn how to use the tools and apply it to everyday work. For the same free open source tools, there are exponentially more videos on the internet that show you how to use them.
So what is stopping organizations from moving to a more agile approach to performance testing? The industry has made advancements in bringing functional testing "up the waterfall" with automation. The same can be true with performance testing.
The Althea Studies Platform is a smartphone and web based SaaS platform for creating longitudinal healthcare studies, i.e. studies that collect data over a period of time. Study administrators can define studies on Althea's web site and deploy the studies as native applications on the iPhone and Android and also on the web for use by study participants.
Learn how automated testing gets down with AltheaHealth's mobile tracker (Android/iOS) using cucumber & calabash
6:00 PM - 6:30 PM -> Mingle & Network
6:30 PM - 6:45 PM -> Introductions
6:45 PM - 8:00 PM -> Overview of AltheaHealth Tracker, Cucumber, Calabash, & Continuous Integration
Food and Drinks will be provided!
I was browsing online deciding on whether or not to upgrade from the Fitbit Ultra to the Fitibit Flex, when it dawned on me. The very first product review is very rarely shared with the public. This review comes from a test report that is used as a deciding factor onto whether or not a product is ready for the general public.
Even though QA is primarily focused on quality, they can become extremely successful when they understand the market for their product. Traditional QA tends to look at defects and whether or not the application matches the requirements. In this ever competing market for product success and market success, QA should start becoming subject matter experts.
To further explore this topic, I will "review" the Fitbit Flex and the Jawbone Up in what I will dub the "Park Hopper Test" cycle. For this cycle, I will walk through the process of developing a simple test strategy and how it can be turned into a review.