The functionality of a messenger app's push notifications is expected to be the same regardless of the device or OS being used. This article discusses how testing these notifications involves keeping in mind the different states of the device and the app, and why the functional configuration audit is just as important as the physical.
When testing, it's easy to call problems with how you'd use the software out of scope, dismissing them as "-ities," like usability, scalability, or security. Some test teams explicitly carve off all these concerns and say they are only dealing with functional testing. Yet the questions raised by this sort of thinking can lead directly to high value for customers.
Typically, industry software testing practice is to separate load testing from functional testing. Different teams with different skills and expertise do their testing at different times and each evaluates the results against its own criteria. We don’t always need to do this in pre-release testing. When time to market is more important than strict accuracy the pilot system can become the load test system while the test team does routine checks during pilot to mitigate risk.
Everyone knows the importance of well-defined functional requirements. We want our products to work, don't we? But how many of us are paying as much attention to defining our non-functional requirements? In this historically focused feature, we learn from past mistakes the potentially disastrous results of inadequately tested NFRs.
The premise behind function testing is to ensure that each program function does what it is supposed to do and nothing else. While it sounds pretty simple, there are some catches you should know about. Michael Bolton examines the twists and turns of function testing and offers some tips for working around them.
Is there an important technical test issue bothering you? Or, as a test engineer, are you looking for some career advice? If so, join experienced facilitators Esther Derby and Elisabeth Hendrickson for "Testing Dialogues-Technical Issues." Practice the power of group problem solving and develop novel approaches to solving your big problem. This double-track session takes on technical issues, such as automation challenges, model-based testing, testing immature technologies, open source test tools, testing web services, and career development. You name it! Share your expertise and experiences, learn from the challenges and successes of others, and generate new topics in real-time. Discussions are structured in a framework so that participants receive a summary of their work product after the conference.
When developing a testing strategy, test managers normally review the business case for the project, study the new requirements, and consider what they know about the system under test. By also including a review of your organization's mission, values, and corporate goals, you will immediately stand out among your peers and at the same time improve the business value of testing. Stewart Noakes has worked with test managers at both large and small companies to help them align test strategies with corporate goals. Using case examples, Stewart describes how they used this process to guide their testing approach and demonstrates how this approach significantly increases the tangible and intangible ROI on testing. Learn to use your company's corporate goals to help you make the right decisions about what to test, how much to test, and, importantly, when to stop testing.
Using a challenging client engagement as a case study, Rex Black shows you how he and a team of test engineers created an integrated, automated unit, component, and integration testing harness, and a lightweight process for using it. The test harness supported both static and dynamic testing of a product that ran on multiple platforms. The test process allowed system development teams spread across three continents to test their own units before checking them into the code repository, while the capture of the tests provided automated integration testing and component regression going forward. He'll also explain the tools available to build such a testing harness and why his team chose the ones they did.
Examine the benefits-and challenges-of implementing an integrated, automated component and integration testing process in a Java/EJB development environment