On many occassions I have dreamed, wished, hoped, our platform was completely automated.  I long for the day when I can just push a button and the testing is done. Wow... wouldn't that be great!  Of course it would... but you need to know a few things before you begin your Automation journey.

Here is some information that can help you answer the questions... should you, can you and will you automate?

• If you are testing the same set of tests for each code release then automating those tests are your best bet.

• If you need to test against code that frequently changes in a timely manner to catch regression bugs then Automate.

• If you are frequently testing significant amounts of test cases on multiple browsers and/or OS platforms, try automating. Automated tests can be run at the same time on different machines, whereas the manual tests would have to be run sequentially.

• Are you testing non-UI aspects of the platform? If so, automation is the way to go.

• If you have the time, money and resources to dedicate to automating your platform, then do so. But remember, not only do you need to create your automated scripts, but you also have to maintain those scripts. Weekly releases of your code could equal a lot of maintenance!

• If you understand that you can’t automate everything, there are test cases that will have to be manually tested. If you have included that additional time into your testing cycle and you can still hit your deadlines, then go for it!

• The type of testing tool you use to automate makes a big difference in what you can and can’t automate. Free tools tend to have more limitations which means less automated scripts and more manual testing. The bigger more robust tools can be pricey, however you will have more flexibility and less limitations which means more automated scripts and less manual testing.

• If you have a few technical savvy Quality Assurance team members that can set up the server that will be the home to your automation framework, and they can troubleshoot and fix issues that arise within that framework, then you are on the right track.

• If you decide to automate do not go into it with the notion that it is the “be all to end all” and all your testing woes will be answered. Automation is a beautiful thing if you are prepared to put the heavy work in from the beginning and continue to do so while you maintain that bounty.

• If you think your Quality Assurance team has what it takes, management is on board and understands that automation will not happen over night, and you are ready to begin that journey, then please proceed below!

Here is a quick test that will help you determine what test cases can and can't be automated:

Is this test scenario automatable?
1. Yes and it won't take but a minute!
2. Yes, but I will be working on this for a week!
3. No, it is not possible to automate

How important is this test scenario?
1. This has to be tested ALL THE TIME!
2. This should to be tested regularly.
3. I only need to test this scenario once in a while.

If you answered #1 to both questions – definitely automate that test
If you answered #1 or #2 to both questions – you should automate that test
If you answered #2 to both questions – you need to consider if it is really worth the investment to automate
If you answered #3 to the first question - I don't think I have to explain to you that your manually testing that one.
If you answered #3 to the second question - it's probably not worth it to automate.

I recently read, AutomatedQA, Pragmatic Software and SmartBear had merged.  Now... as I do consider myself a "semi-computer nerd", I'm not really interested in reading about mergers and acquisitions. But this story caught my eye.... 

When I finished reading the article, one word popped in my mind... "genius".  What a solid and creative plan to pull together 3 tools that every software development shop would need.  An Automated test and performance tool, a requirements and defect tracking tool and a code review tool... like I said "genius".  And get this... they are affordable to even the smallest development shops, making integrated automation accessible to the masses! 

I checked out their ALM Complete product and I was extremely impressed by what it offers, Project Management, Performance Management, Requirements Tracking , Defect Tracking, Collaboration and Reporting. 

Believe me, I know times are tough and companies tend to lean more towards free shareware options, which is the route we take here at ThePort.  But if you do have a small budget and want a more robust tool that would cover all your needs, take a look at what they have to offer.  They pride themselves on being an affordable solution and spend the time differentiating themselves from the "big" automation providers.  Another "genius" move!

You can check out the full article at:  www.sdtimes.com
To learn more about the software offered by Pragmatic Software, SmartBear and AutomatedQA click here!

What Makes A Good Leader? 4 Essentials
Software Test Professionals asked the speakers who are presenting at the Software Test Professionals Conference & Expo 2010 in Las Vegas several questions about leadership. When asked about the top characteristics of strong leaders in the testing field, the conference speaker’s highlighted four main attributes they considered important.



1. Knowledge of the Business
Linda Hayes, Worksoft, Inc. founder states, “It’s important that leaders have a solid grasp of the business drivers and risks.” Often times, people focus on the process to manage a testing department and don’t have a grasp on the higher level business objectives. Leaders should have a deep understanding of the complex needs of the stakeholders including the customers, the organization and the team.



2. Communication & Interpersonal Relationship Skills
It’s not enough to simply have knowledge of the overall business. The ability to share this information with your team is also important. Jim Hazen, Consultant from Connected Testing stated “…listen and talk to people within and outside your group … you don’t have to be a diplomat but you do need to be able to convey information clearly.” A leader who is able to convey information clearly inside the testing department as well as outside and at all levels will serve as an information bridge to close the gaps of miscommunications and build the testing department’s value to the organization. Furthermore, clearly conveying information helps to motivate and support the testing team, create positive morale and provide a clear vision for success.



3. Knowledge of the Technical Skills
Robert Walsh, President of EnvisionWare, Inc. states that “Leaders must have a good balance between communication and technical skills.” With balance, a strong leader who understands the testing process, tools, systems and solutions can help guide team members without getting involved in the tactical aspects of the project. A leader’s ability to use this technical knowledge to be decisive and lead the team will inspire the team’s confidence in their leader.



4. Strategic Skills
Operating in environments with heavy workloads and not enough resources can challenge a senior leader in testing. It’s important to carefully organize resources to match priorities. In order to successfully allocate resources, a leader must have a clear focus on the testing department’s end goals and maintain a visual above the minefield. When a leader understands both human and technical resource allocation they can most effectively be open-minded to revolutionizing change for the betterment of the organization. Bradley Baird, Principal SQA Engineer at Symantec summarizes, “Just because we did it that way last time doesn’t mean we should do it that way this time. Be open to ideas on how to improve processes and procedures.” With an open mind, clear vision and the ability to effectively allocate resources, strategic leaders can drive change and lead their teams into the future.



 

Check out the article in Software Test Professionals magazine about the difference between 'Quality' and 'Testing', and why it's important to set/measure standards for both.

http://www.softwaretestpro.com/Item/4768/Quality%2c-Not-Testing/Quality-Assurance-Test-and-QA-Testing?utm_source=Email&utm_medium=email&utm_content=060810-TQA&utm_campaign=NEWSLETTERS