Here are some such notables from the week of Feb. 23, 2015:
Hot on the heels of the recent Introduction to Security Testing and Build the “right” regression suite using Behavior-Driven Testing (BDT) webinars, uTest University is offering a chance for testers to get familiar with Android testing. The webinar is taught by Iwona Pekala, a Gold-rated uTester and frequent contributor to the uTest Forums.
In this webinar, participants will learn how to:
- Prepare your mobile device and PC for testing
- Install applications
- Record videos and take screenshots
- Collect logs
- Get information about the types of crashes
Today, uTest University launched the beta of the “Test Your Knowledge” feature on select courses. You can now take an optional quiz at the end of a course to see if you understood the information presented. Your score can be emailed to you, and you can choose to share your quiz results on social media so that other uTesters can see how you did!
The first two courses in the beta quiz program are Accessibility Testing 101 Tutorial: Finding Color Contrast Ratios and What is White Hat vs. Black Hat Security Testing?
In the Accessibility Testing 101 Tutorial, expert Helen Burge explains the concept of color contrast ratios, why it’s important and how to determine the color contrast ratio on a web page. At the conclusion of the short video, a five-question quiz tests to see if you learned the information.
uTest is excited to announce another live webinar opportunity. Registration is now open for the webinar Build the “right” regression suite using Behavior-Driven Testing (BDT), with Anand Bagmar. In this webinar, participants can learn:
- How to build a good and valuable regression suite for the product under test
- Different styles of identifying / writing scenarios that will validate the expected business functionality
- Automating tests identified using the BDT approach will automate your business functionality
- Advantages of identifying regression tests using the BDT approach
Anand is a familiar guest blogger on the uTest Blog. His recent post Selenium: 10 Years Later and Still Going Strong takes a look at the ecosystem that Selenium has nurtured over the past decade.
From time to time, the uTest Blog highlights some of the recent blog entries that uTesters have crafted on their own personal blogs, along with some standouts from the outside testing world.
Here are some such notables from the week of Jan. 23, 2015:
Blogs This Week from uTesters & uTest Contributors
- Reading Recommendations #2: Continuing on last week’s theme of uTest contributor Daniel Knott’s favorite blogs of recent, he once again put together this list of 7 new blogs. They include topics in areas as diverse as expectations when speaking at conferences to designing products for wearables. One recommendation even includes a recent post from one of our own uTesters about knowing one’s testing profile.
- Experience is Earned, Expertise is Granted: An ‘Ask the Expert’ interview we ran earlier in the week with Michael Larsen prompted this follow-up blog. It’s a great read and questions the very notion of ‘expert,’ and whether anyone can proclaim themselves as one, or if the moniker has to be imposed from the outside.
In my opinion, the role of the tester is evolving. When I started testing in 2002, I had no contact with the users or developers. As a result, I had a limited view of the system and what it could do. This limited view also translated into what was expected out of me. As a tester, I was supposed to find defects, and that’s what I did.
However, at least for many people, things have changed, and they have changed for good. Testers are often part of an integrated team now and their role is not limited to find defects. They help teams with whatever they can — from clarifying the requirements to streamlining the release process. Whatever it takes to deliver good-quality software, testers are expected to do that.
I believe the role of a tester is evolving from being a bug hunter to an opportunity hunter. As a tester, we hunt for opportunities that:
- Make products useful and usable
- Improve the efficiency of delivering software
- Increase prospects for the business
We publish a lot of content here at uTest not only on our Blog (which you have the distinct pleasure of now reading), but in our Forums and uTest University as well. But there’s also a lot of great content out there that catches our eye on a daily basis.
From time to time, the uTest Blog will highlight some of the recent blog entries that uTesters have crafted on their own personal blogs, along with some standouts from the outside testing world.
Here’s some of our favorites from the most recent week.
Many in Boston are dreading the logistical nightmare of an Olympics built around a 1600’s era, Pilgrim-founded roadmap that confuses even people that live in Boston. However, we here at uTest have Olympics Fever from the prospect of the 2024 Games being in such close proximity to our headquarters, which got us wondering: What would a testing-themed Olympics Games consist of?
Here are a few events we proposed could actually take place during the ‘Testing Olympics':
- Spear-throwing for bugs: Tester-athletes would be armed with spears, chucking them at targets of bug classics, including “Heartbleed”
- Usability Testing…With Trampolines: Testers of various strengths and sizes would put their jumping abilities to the test…along with their usability testing skills…by testing out the weight and build quality of new-to-market trampolines
- Greco-Roman Wrestling…With Developers: Testers would be able to take out their pent-up frustrations with developers by wrestling them Greco-Roman-style for Gold and glory
Which event would you want to see most at an Olympics comprised of tester-athletes?
If QA teams don’t make the most of their reporting efforts, they will squander a golden opportunity to enhance the quality of their software development practices.
The reporting phase of the software testing process is one of the most important aspects of quality assurance and testing. Identifying critical bugs, defects and performance issues will not provide much value to the development team if there isn’t sufficient documentation outlining what the flaw is and how it can be reproduced. By taking a lax approach to reporting, QA teams will hinder their own testing efforts, costing the organization time and money.
Simply reporting on test results and discovered bugs isn’t enough. Software testers need to ensure that they are making the most of these efforts and providing actionable information to developers and other team members. Nothing is more frustrating to a QA expert than receiving a bug report that offers little insight into the nature of the flaw or how one can go about recreating it.
Software Testing Fundamentals explained that one of the most important criteria for effectively reporting flaws is to be specific and detailed.
“Provide more information (not less),” according to the publication. “In other words, do not be lazy. Developers may or may not use all the information you provide but they sure do not want to beg you for any information you have missed.”
The holidays are here, and you know what that means. Plenty of forced conversations with extended family and awkward exchanges with that one aunt that always has a little too much spiked egg nog. But the holidays don’t have to be quite so frightful (unlike the weather outside). In fact, they are a joyous and festive time for many people — especially our testing community.
On that note, our uTesters recently discussed some of the tech gifts on their wishlists this holiday season. Here’s our community, in their own words on what’s on these lists: