Convert testing data into valuable project information.

Joel Montvelisky wrote an interesting piece on the art of transforming testing data into project information. In his article he showed different examples of test execution reports and explained why report B was better than report A. He noted that when you work with people outside of your testing team, you must also think like them, understand the information they need and how to to display it in a way that they will grasp the content faster and better. 

Here are some examples of test execution reports:

Team A’s Report:
Total Tests in Cycle: 376 
Passed Tests: 301
Failed Tests: 28 

Tests not Run: 57

Team B’s Report:
Tests in Cycle: 376
Execution percentage: 87.5%
Passed percentage: 80%

Which report is better?

While both reports are providing the same data, report B supplies the readers with better information. The advantage that report B has on report A is that it shows the percentages in their report. This is an advantage because people don’t like doing math equations in their heads, when they can just read it like in Team B’s report.  The less people need to think, the more brilliant your report will appear to the intended audience.

Key tips for test execution reports

  • Show data in percentages or rates
  • Use graphs
  • Don’t pollute the report with useless data
  • Anticipate questions
  • Report should speak for itself. Less explanations = good report.

Read More

 

From the blog CS@Worcester – My Blog by justcodeit94 and used with permission of the author. All other rights reserved by the author.

4 Keys to Better Test Data Management

Original Article by Jeffrey Hughes

Finding proper test data for testing the software you’re developing for can be a challenge most of the time for a variety of reasons. In his article, Jeffery Hughes goes over why test data management is important and lists four main ways of how to improve your management of test data.

Hughes states that test data management is important because it can help address challenges that occur in providing test data quickly and continuously for the application you’re working on. The main three challenges that he touches on are test data compliance, availability, and freshness.

After that, Hughes addresses what the four keys to better test data management are. The first key is how to properly discover and analyze test data. Hughes states that your test data may be spread across multiple platforms and could be extremely time consuming if you tried to access it all manually. He suggests that using a tool that can make sure that the right test data is being tested and to come up with a “solution that provides complex coverage analysis and data visualization is a better approach.”

The second key that Hughes talks about is protecting sensitive data. In this section, he points out that is important make sure that sensitive data is being properly secured (even when just in testing), and to make sure that you use “inconsistent data to test for anomalies that are sure to occur with end users.”

The third key is make sure that you’re able to deliver test data on demand. Hughes points out that it is a great advantage to have your data stored on a central repository so that all test data is in one place and can be easily shared. The hope is to make sure that there are no more bottlenecks for testers that are “waiting for data” when running tests.

Finally the fourth key is to make sure that you try to automate as many steps as you can. Hughes suggests severally tools that can make automating your testing easier for your and your team. He states that this kind of “stabilized automation framework guarantees that data will be provisioned in the right state when needed by your testers.” This also makes it easier to trace your data and test cases back to their requirements, and also means that if your “requirements change, the data can be updated automatically.”

From the blog CS WSU – Techni-Cat by clamberthutchinson and used with permission of the author. All other rights reserved by the author.

Old School Testing

We as humans are naturally built to adapt to changes. One of which includes the adoption of new forms of testing techniques for program testing. In today’s modern technological society, you would be crazy not to take advantage of the various benefits automation testing has to offer. Like, why do the testing by hand when you can have a computer do it for you?

I read an article this week that addressed that very same question; why do we need manual testing? The article entitled “13 Reasons Why Manual Testing Can Never Be Replaced” (http://blog.testlio.com/13-reasons-why-manual-testing-can-never-be-replaced) sheds some light on why manual testing should still be a relevant and significant form of testing. Out of the 13 reasons that were mentioned, there were particular ones that stuck out to me. One reason was that “bugs are found where you least expect them” meaning that by manually testing, you may find bugs you weren’t intentionally trying to find which can’t be done with automation testing because it can’t catch issues that the testers themselves, are unaware of. I found this quite refreshing because its true; tests cases can’t exceed the scope the developer intended it to have. Another reason I found to be interesting is that “mobile devices have complicated test cases”. This is something that can quickly become a nuisance because while an automated test case may take a while to program and create, manual testing for that same test case may take much less time and effort. So while new technological developments are progressive and useful, sometimes you just got do things old school.

From the blog CS@Worcester – Tan Trieu's Blog by tanminhtrieu and used with permission of the author. All other rights reserved by the author.

It’s A New Dawn, A New Day, A New Life…In Testing (10/28/16 Week 6)

And it feels soooo goooood!

What’s good? When we people get to do their things their own way. Where there are no strings or repetitive procedure to tie down the curiosity of the human mind. The fact where you do not have to ask the same questions over and over again, or drive to the same location every weekday  or even ordering the same cheese pizza with no toppings. You are you, and switching everything up makes life feel refreshing again. This principle isn’t just in one’s daily life, but can also be applied to the average software tester.

d25c45e5362e4789a710570edcb99f80

When you start as a software tester, you are probably very excited of the day ahead eager to begin your new chapter in life. That’s great! Keep that spirit up, because when you start out testing, you are mostly like going to be given the same test cases over and over again hence the mighty potential to drain your energy for the love of testing. But don’t let that get to you at all, it doesn’t have to be that way! Even though in the end orders are orders, its worth taking a leap of faith and dumping all of those repetitive test case procedures, and start making you own documentation!

Yes, you may be new so you may not have enough experience to derive your own test cases. But that does not mean that you are not skilled! Many reasons why one would want to make new test case documentation from scratch could either range from new testing environments, new or modified code, and more importantly, its a lot more fun!

The next time you use old repetitive test cases, make sure you do whatever you can in your power to use newly developed ones by yourself instead. After all, being a software tester includes doing whatever it takes to make stuff work right. Nothing hurts when it comes to a slight bit of change.

(Source : http://www.testthisblog.com/2016/03/start-from-scratch-vs-old-test.html)

From the blog CS@Worcester – Dan's Tech Rant by danbarbara and used with permission of the author. All other rights reserved by the author.

Agile VS Traditional Testing    

Agile testing demands more from its testers, therefore places a higher value upon them. Here are several factors that come into play in the comparison.

Continuous Involvement

In traditional projects, it is mostly solo working with little to no interaction between developers and teams. But in agile, the test team is integrated with the Scrum team in order to be continuously involved. This includes discussions, meeting, constant interactions, etc.

Essential Tools

Agile requires more tool support than the traditional method because of the increased pace in development along with the continuous iterations. Each iteration carries over previous iterations that have to be automated quickly.

Multidimensional Skills

Traditional projects have set expectations that never really change. It’s bland. An agile tester’s viewpoint has to not only include the functional aspects of testing but advise on design discussions, usability efficiency, and reviewing installation guide steps.

Effective Communication

Agile requires greater communication skills than traditional because of the key role of effective communication among team members at all times. Testers act as the binding force of the team when they work in pairs with developers through sharing their test cases and ideas.

Quick Feedback from Testing

Agile timeframes are shorter than on a traditional project, and testing already requires feedback on a regular basis. Agile requires daily stand-up meetings, design discussion or review meetings.

From the blog CS@Worcester – Kyle Polewaczyk by kpolewaczyk and used with permission of the author. All other rights reserved by the author.

Week 6: “How to Solve the Common Web UI Test Automation Problems”

I found the blog, How to Solve the Common Web UI Test Automation Problems Using the Katalon Studio Free Toolset interesting this week.  Although I initially had no clue was Katalon Studio was, this blog enlightened me on what exactly it is.  The blog starts off with stating a few things that are common problems found with web UI automation.  It says, “Wait-time issues, Iframe Issues, pop-up issues in automation, and issues in locating deeply nested elements”.  I am pretty familiar with UI automating and I know exactly what they mean when they say wait-time and pop-up issues.  You could have an automation working perfectly, but as soon as one unexpected pop-up comes up; the whole test is going to fail.  It talks about what a simple “wait” is when automating.  Wait is basically a pause in the automation which gives the system time to load or do whatever it needs to do to carry on.  Katalan Studios is a tool that generates test script that helps your automation from failing.  For example, if an alert keeps randomly popping up, you can use Katalan Studios to help you handle those issues.  The blog didn’t go into too much detail about Katalan Studios but it talked about some cool things that it is capable of doing.  Now that I am aware that this type of tool exists, I may even use this tool at work someday!

From the blog CS@Worcester – Alex's Comp Sci Blog by alexsblog13 and used with permission of the author. All other rights reserved by the author.

Week 5: What Scared Testers Most?

With Halloween around the corner, the blog The Tester’s Horror Stories (Halloween Special) interested my this week.  The blog talked about the different types of things that can be very frightening to a tester.  It listed things like:

  • Buggy software
  • Inferior Test Environments
  • Missed deadlines
  • Feel underappreciated
  • Breaking bad news
  • Catching up newer technologies
  • Onsite-offshore model
  • Accidentally turned ON/OFF or deleting something
  • Low status in the industry

I personally have been a victim of accidentally deleting something.  I had all of my test results recorded for a huge section of the product I was testing.  Unfortunately, I accidentally deleted the file with all of the information and had to redo everything.  It was by far a tester’s worst nightmare.

The writer of this blog tells the story of how he was extremely good at documentation and could get everything written up extremely quickly.  The tester went into work the day after everything was completed as he usually would.  He was called first thing in the morning into a meeting with the manager and was asked why he had written up so many invalid bugs.  The news was already spreading to the client and the manager needed an answer instantly.  Obviously as a tester it is extremely important to always make sure the bug is actually valid before you go ahead and write it up.  However, I liked how this blog more touched on the fact that you need to be able to hold yourself accountable to any mistakes you may make as an engineer.  If your name is on it, you need to take full responsibility and explain what was going on and why you did what you did.  Humans make mistakes and most of the time it won’t be the end of the world, but not owning up to it is a lot worse.

 

From the blog CS@Worcester – Alex's Comp Sci Blog by alexsblog13 and used with permission of the author. All other rights reserved by the author.

Ultra Code 2016-10-25 10:51:00

Ankit
  • Week 3 – 7 October

Cross-browser Web testing tools

At this thime, there is a huge collection of competing browsers. In this situation, there are no common standards for displaying sites: each one of them may display a site in its own way, for example, by distorting the page content. Due to this fact, the “cross-browser” term emerged, that is the feature of a site to be displayed identically in all browsers.Although the cross-browser issue emerged rather recently, there already exist a great number of tools for testing it.All cross-browser testing tools are different  in the number of supported browsers, ease to use, price, and also testing speed. These factors greatly complicate the choice of the suitable tool.This article is devoted to the problem of choosing the right cross-browser testing tool. It lists the popular tools, their advantages and disadvantages.This article would be useful for testers, who haven’t performed this kind of testing yet, or for people, who face the problem of choosing the suitable tool.BrowserShots gives the possibility to test a site not only in five most popular browsers, but also in less known browsers, such as Netscape, Avant, SeaMonkey.

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ultra Code 2016-10-25 10:51:00

Ankit
  • Week 3 – 7 October

Cross-browser Web testing tools

At this thime, there is a huge collection of competing browsers. In this situation, there are no common standards for displaying sites: each one of them may display a site in its own way, for example, by distorting the page content. Due to this fact, the “cross-browser” term emerged, that is the feature of a site to be displayed identically in all browsers.Although the cross-browser issue emerged rather recently, there already exist a great number of tools for testing it.All cross-browser testing tools are different  in the number of supported browsers, ease to use, price, and also testing speed. These factors greatly complicate the choice of the suitable tool.This article is devoted to the problem of choosing the right cross-browser testing tool. It lists the popular tools, their advantages and disadvantages.This article would be useful for testers, who haven’t performed this kind of testing yet, or for people, who face the problem of choosing the suitable tool.BrowserShots gives the possibility to test a site not only in five most popular browsers, but also in less known browsers, such as Netscape, Avant, SeaMonkey.

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ultra Code 2016-10-25 10:51:00

Ankit
  • Week 3 – 7 October

Cross-browser Web testing tools

At this thime, there is a huge collection of competing browsers. In this situation, there are no common standards for displaying sites: each one of them may display a site in its own way, for example, by distorting the page content. Due to this fact, the “cross-browser” term emerged, that is the feature of a site to be displayed identically in all browsers.Although the cross-browser issue emerged rather recently, there already exist a great number of tools for testing it.All cross-browser testing tools are different  in the number of supported browsers, ease to use, price, and also testing speed. These factors greatly complicate the choice of the suitable tool.This article is devoted to the problem of choosing the right cross-browser testing tool. It lists the popular tools, their advantages and disadvantages.This article would be useful for testers, who haven’t performed this kind of testing yet, or for people, who face the problem of choosing the suitable tool.BrowserShots gives the possibility to test a site not only in five most popular browsers, but also in less known browsers, such as Netscape, Avant, SeaMonkey.

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.