Top 5 Time Management Tips for Testers

We’ve all been there. The week when you are bogged down with so many projects you have to stay late and wake up early in an attempt to catch up on work. As a tester you have to deal with managing developers’ perceptions of code, trying to convince them there is a bug in the code all while running load tests, monitoring the application and identifying bottlenecks. There’s just not enough time in the day to get what you need done.

To help you we have gathered the top 5 time management tips testers use to maximize their time and get projects out the door.

1. Planning is essential

When you are tasked with multiple projects, planning is essential. A great place to start is simply planning your day. Get in the habit of starting each morning by writing a to-do list. You can keep a running to-do list on your computer in a note-taking application or word processor. Or you can go old school and keep a pen and paper close by to jot down the tasks you need to complete. According to the Huffington Post, the very act of writing things down gets placed in your long-term memory making you more likely to remember.

Make sure to clean your list from time to time and eliminate anything that just isn’t getting done. Always ask yourself: Is this meeting necessary? Can I delegate some of these tasks to another team member? Do I need to schedule appointments?

Get good at planning your days and you’ll find that your project planning skills will also quickly improve.

To read more about Top 5 Time Management Tips for Testers click here.

Hybrid Development for Mobile Apps – Neotys Testing Roundup

TJ VanToll is a web developer, speaker, and writer living in Lansing, MI and working as a developer advocate for Telerik. He is an open source advocate that is on the jQuery UI team, publishes his blog open source. TJ is also the author of an upcoming book jQuery UI in Action. In this interview, he shares his opinion on hybrid development for mobile apps.

InfoQ: In your opinion, what are the most important stumbling blocks to the use of hybrid development?

VanToll: The one that commonly comes up is performance, and I would say the other big one is debugging, so performance has notoriously been a problem for hybrid development and I think that goes back to the bad or older phones that were out there, some older devices where hybrid development was just terrible, it really didn’t perform well.
In terms of how you can actually overcome that, you look at some of the libraries that are coming out today, things like Ionic and Kendo UI Mobile, there are some UI frameworks that are specifically designed for building these hybrid mobile UIs, they take into account things like using a fast click to get around the 300 millisecond click delay and building some really responsive UIs because if you go back a few years when you developed a hybrid mobile app you would use the exact same technologies that you would use to develop a web app, which works just fine, it’s still the web, so the same libraries will work, but having a library that is specifically catered to build a certain hybrid app can overcome some of the problems that have historically been associated with it.

To read more of VanToll’s interview click here.