When a networked device is physically attached to us and works with us and through us, the more personal, even emotional, the interaction is. With wearables, the user becomes a part of the Internet of Things. Author Gerie Owen participated in the 2011 Boston Marathon in which participants had a wearable attached to their clothing. Long story short, not all of the RFID chips, meant to track runners’ exact race time, registered with the readers.
Owen’s time wasn’t recorded, resulting in not only disappointment, but also a drive to determine what had and had not been tested as well as the impact of the failure on the user. She realized that wearables’ purpose or function is directly tied to human interaction, which creates the need for human users to play a role in wearables testing.
For a look at the method Owen devised to test this collaboration, read her full article here.
Agile development moves fast, I mean, that is the whole point after all. The notion of speed is embedded into the very fabric of Agile, so why then, does performance testing often get saved for the end of the Agile Development process? This usually happens as a direct result of misconceptions people have about what’s possible with respect to performance testing in an Agile setting.
This post explores six different misconceptions about load testing in an Agile environment and provides some helpful ways you can address them in your organization. Read it here to learn how you can push your performance testing initiatives deeper into your Agile process, improving your application and making your end users happy.
“Either fix me or delete me, but do not forget about me!”
Have you ever wished for sentient tests? This write-up comes from Mauri Edo, a QA Engineer at Bamboo, and it’s written from the perspective of an @ignored test. If you’ve ever annotated a test as such and then abandoned it, this post might hit you right in the feels.
Of course, the test starts out grateful, simply happy to exist and perform its job of finding bugs. But then it begins to fail, sometime causing red builds. It becomes flaky, thus earning it an @ignored annotation. Frustrated from being ignored, this test is striking back with an open letter urging developers to give it the attention it needs to provide value again.
An entertaining read, to say the least, this post will tug at your testing heartstrings. Check it out!
4. Discussion: Things Testers Say or Hear a Lot?
Perk up your ears in the office and take note: what are testers saying? Every profession has its own “jargony” phrases that tend to pop up quite frequently. So what do you find yourself saying? What are some of your fellow testers’ favorite lines?
Here are some examples for inspiration:
“If the business is going to do that, I can’t provide assurance of the quality of your code.”
“I don’t care if it works on your machine! We are not shipping your machine!”
“It worked the last time we tested it.”