It’s bin a long time since I wrote my last blog post. At the moment there is not so much time for me to write down all the posts I have in draft mode. Sorry for that! However, since christmas is almost there and the german edition of my book Hands-On Mobile App Testing is available since end of September with the title Mobile App Testing, I want to give all my german speaking blog readers/ lurkers 😉 the opportunity to win a signed copy of the german edition.
Today, I want to try something new. Maybe you have read my blog review 2015 in December and you have noticed that I wrote 104 blog posts in 2015. However, I want to scale the amount of blog posts on this blog and therefore I need your help. I am looking for guest blog posts like the one from Brian Hamilton or the one from Joel Montvelisky.
If you are working as a software tester, software engineer in test, scrum master with a focus on high quality software or you are a product manager who loves to ship high quality product this might be of interest for you. Maybe you want to share your knowledge in a guest blog post here. However, there is no need to be an expert in your role, I would love to see guest blog posts from every level of experience, from junior to senior. From my point of view it doesn’t matter which skill level you have, I think that everyone has something to share :).
Maybe the guest blog posts on my blog will help you to develop your writing skills and will help you to learn more about the area you are working in. So if you are interesting in writing an guest blog post, please get in contact with me. You will find my email in the about me section.
This is the third post of my smartwatch app testing series and in this post I will write about Pebble OS. In the previous posts I wrote about Tizen OS and watch OS. I think we all know the Pebble watches from their success on the Kickstarter campaign in 2012. In this campaign the company Pebble Technology Corporation raised more than $10 million dollar which was the best Kickstarter project at that time. With the raised money the company was able to produce the first Pebble watch. Since then, Pebble launched different versions of their smartwatches and the concept is different compared to Tizen, watch OS or Android Wear. Pebble’s characteristic is the low power e-ink display with either 2 or 64 colors. Right after the start of the first Pebble and the Pebble OS, this platform has become more and more attractive in the smartwatch business and therefore it is important to know the platform details in order to develop or to test for this system.
The following article “2016 Will Be the Year for Wearables So Test Wisely” is a guest blog post by Eran Kinsbruner who is the Mobile Evangelist at Perfecto, one of the leading mobile cloud and automation companies. This article is the introduction to my smartwatch app testing series which will start next week.
You don’t have to look far to see the digital transition in practice. Airlines, banks and retail giants are making their products available on various digital platforms to satisfy their customers, grow their business and compete in a challenging market. Wearable devices such as smartwatches and health and fitness trackers will continue making progress in 2016. According to an IDC report, basic wearables such as fitness trackers are growing by 76% year-over-year, while smart wearables like smartwatches are growing far faster.
This time in the “People in Testing” series, I had the chance to interview Dan Billing also known as “TheTestDoctor” on twitter. Dan has been a tester for 15 years, working within a diverse range of development organisations, mostly in the south west of England. He currently works as a test engineer at New Voice Media, where most of his time is spent working on the security testing needs of the business. This includes mentoring, supporting and training members of the team to use these skills also.
Daniel: What is currently your biggest challenge at work?
Dan Billing: Learning and developing skills and strategies in application security are my main challenges in testing. Without talking about technical or business specifics, the issues include ensuring that test design, strategies and processes are created that are appropriate to the organisation and our compliance obligations.
Part of my role is also to enable members of the team to do security testing. I will consult with the other feature teams. I’ll enable mentoring and learning where needed. I often set up internal workshops, one to one sessions, test collaboration, documentation and blog posts on security testing matters. It helps develop skills around the team, so that one person isn’t a blocker to getting things done, and can get started in their personal learning.
Skills development is a huge problem for organisations that are trying to build up their test strategies to include security, usually where it wasn’t considered in the past. Quite often security testing is considered an afterthought in development organisations, or it is outsourced to specialist third party consultancies.
Penetration testing and security experts are generally extremely expensive to recruit into teams, either because of rates of pay, or because the people you want to hire just aren’t easy to find and recurity.
Also recently we have seen a number of high profile hacks that have brought the most basic security vulnerabilities into sharp focus. Both the Talk Talk and the VTech hacks were done using SQL Injection, which is common, easy to identify and exploit. If it is easy for the hackers to find these vulnerabilities, why not testers too?