1. Shutting Off the Noise – Why Meditation is Good for Testing
With the help of up-and-coming websites, apps and other informational material, meditation is becoming a widespread practice—and it might be time for all you testers to try it out. Author and tester Joel Montvelisky initially tried meditation as a way to combat the difficulties he was having concentrating and completing things with all the distractions/noise/multitasking flying around.
Over the past couple weeks, he noticed that meditation actually helped him test better. Read on in his insightful article here to explore the testing benefits he’s reaping from meditation.
2. How Mobile Development and Testing Inform the Rest of the Industry
The past informs the future, and even though the software development industry has evolved to accommodate the Internet of Things and mobile devices, testers have been able to successfully apply proven web testing techniques to these new technologies. However, it’s not enough to simply observe how the past informs the future—it’s imperative to note how the future is helping people better test and develop on what’s come before it.
In this article, author Josiah Renaudin quotes Prathap Dendi, Vice President of Business Development at Electric Cloud, who argues that there are three main lessons we’ve learned from mobile development and retrofitted to other facets of the industry: user experience, cloud-based services and speed. Read on here for a deeper dive into these facets and how they’re informing the industry.
3. 4 Performance Testing Fallacies Affecting Your Testing Strategies
In the past, software development teams were more inclined to push off performance testing until the end of the development cycle or even forgo the practice completely. Quickly, application performance has become a major factor in attracting and retaining users. As a result, performance testing is no longer optional.
While an increasing number of organizations have adopted performance testing strategies, there are still misconceptions floating about that may prove detrimental if not addressed. Just adding hardware, overconfidence, failing to understand the difference between speed and perceived performance and an absence of errors are a few fallacies that can trip up development teams. Check out this article for a look at each and how they may be negatively impacting your testing strategies.
4. Discussion: If you had a month to train up a new tester, what would you do?
When you bring new testers into your organization, there’s usually some sort of ramp up period. The training time required will obviously depend on the tester’s skills and understanding of your application(s), however, it’s wise to have a basic strategy in place for training new testers who join your team.
Rosie Sherry is interested in learning about the practices, techniques and approaches you have or would use to get a new tester up and running.
What do you do to help them get started?
What skills do you think are super important?
What knowledge should they have or look to have?
Do you have a solid training policy in place? Contribute to the discussion here!