Archive for the ‘Software Testing’ Category

The future of the software tester role

Tuesday, July 10th, 2012

 

 

 

 

 

 

Silvia Nuñez – SQS Marketing Manager

 

The Future of Testing is a subject always, in some way, discussed at QA&TEST. What will the future bring in our profession? Some people make quite negative prediction but others consider that, as the development of software continues to evolve, so will the testing, trying to continue providing the added value that it gives today.

We understand that the future will change methods; the role of the tester will be different, etc. We recommend reading these two articles addressing this issue and we invite you to discuss with us your perceptions about the future of our profession. How do you consider the future of testing, and particularly our role as testers in it? What characteristics do you consider that a tester should have to continue adding value to their work in the future?

Article 1

Article 2

 

Everyday Exercise for the Technical Test Team

Wednesday, March 28th, 2012

Mr. Bob Jonesis an experienced automated test engineer and advocate of agile testing. In this article published in StickyMinds.com, he gives us some interesting  tips and advices about how not to loose the motivation when creating and being part of a Technical Test Team. This is an interesting and different point of view that we would like to share with you:

“Very often, starting something is much easier than sticking with it. This is just as true for growing a technical test team as it is with gym memberships. At first, a couple pounds come off easily and you get interesting muscle aches. Motivation is high, and you scoff at others who fail to keep their exercise routines. During the initial period of automation high, you build new tests, and everyone is excited about the new skills. It is important to celebrate your early victories—those first bugs found by your automation feel great.

But real life can intrude and kill the passion. Sprint work, family life, and other interests all can get in the way. For continued success and growth, you need to plan time for automation (just like scheduling a regular time for the gym), and plan for more audacious goals.”

Read the full article here.

DATABASE TESTING – Properties of a Good Test Data and Test Data Preparation Techniques

Thursday, March 22nd, 2012

 

Database is one of the inevitable parts of a software application these days. Moreover, as the complexity of application increases the need of stronger and secure database emerges.

 

In the section “Action/Steps” of the Test Cases, we must mention the acceptable data as input for the test. The data mentioned in test cases must be selected properly. The accuracy of “Actual Results” column of TC Document is primarily dependent upon the test data. So, step to prepare the input test data is significantly important.

Read the full article here.

The cost of automation

Friday, February 10th, 2012

Testers: Put on Your End-user Hat

Wednesday, February 8th, 2012

One of the biggest criticisms about testers and QA organizations is that they do not understand the business or the end-user. If you believe this to be true, it sends a clear message about not having a value-adding testing team of professionals. The more you know about the ultimate customer or end-user, the more you will become an effective, risked-based tester.

When I led QA teams in the past, I made “knowing your customer” a major performance criteria for my staff. To ensure this, I arranged field trips with business development to customer sites and had the testing team view how and why the end-users actually used the system or application. Upon returning from these field trips, the QA team started to modify how it approached end-to-end and user acceptance tests. It was so beneficial that the number of critical end-user defects dropped by more than 20 percent in a very short period of time.

 

Continue reading Paul Fratellone’s article at Sticky Minds.

Seven deadly sins in SW Testing

Friday, February 3rd, 2012

Testers with Asperger’s Syndrome

Monday, January 30th, 2012

There are more and more companies in Europe that hire testers with Asperger’s Syndrom or autism.  This practice has advantages and inconvenients, and the best way to discover them is talking to a person affected by this syndrome. Tirsh Khoo, tester in Sydney for a known management platform of email campaigns, has arranged an interview with Michael Drejer, who has Asperger syndrome and works as a tester in a company in Denmark.

Click here to read the whole interview.

Smart grid: What’s here, what’s needed, and what you should know now

Monday, September 27th, 2010

Let’s define the smart grid as the infrastructure and technologies that enable integration of the consumer and distributed resources (generation, renewables, storage, demand response, load control) with the operation of the entire grid and electricity markets, while also improving the reliability and Security of the overall electric service. The biggest gap is the lack of inexpensive, standardized, and ubiquitous communications that deliver bandwidth, extreme reliability, and security for both control and management applications as well as basic information management and sharing applications. This broadband communications infrastructure does not need to be one technology, but it needs to extend all the way from central control systems to end-user devices.

Click here to read this whole article at Embedded Computing Design.

The golden rules of managing software projects

Tuesday, September 21st, 2010

We asked what looks to have been a pretty contentious question – what’s the role of managers in software development? – and we got some pretty contentious answers, which are well worth a look in their entirety. The conclusion: a lot of managers are crap. But – and it’s a big but – they don’t have to be, if they get certain basics in place.
Here are your very own top five golden rules, compiled from your comments, which managers can employ to build trust and get the best out of developers. These rules may seem like common sense, but we know from the feedback that they are as frequent as a night bus.
1. Protect the team from unnecessary distractions: A manager’s job is to help the developers to work as productively as possible towards logical and achievable project goals by protecting the team. He must also earn the team’s respect by fighting heroically for them against the boneheaded stupidity to be found in swampy stagnant meeting rooms across Britain.

Click here to continue reading this article at  The Register

The Impact of Automation on Development

Thursday, September 2nd, 2010

It seems obvious that automation will affect the test organization. Less obvious—but no less real—is that it will also affect the development organization. In fact, when you choose to automate the testing for an application, your relationship with development changes completely.

Think about it. Manual testers only have to be able to interact with the application using the screen, keyboard, and mouse or other device. Automated test tools, on the other hand, have to interact with the software at a deeper level, thus exposing the inner workings of the code and perhaps uncovering problems that prevent or complicate automation. If you’re not careful, developers might think you have suddenly transformed into an interfering busybody who is sticking your nose into their business.

This shift in your relationship with development can be handled in a bad way or a good way.

Click here to read this article at Sticky Minds.

Live Chat

Join the Live Chat