A Tester’s Nightmare: Halloween Edition (Week 7 11/4/16)

No tester can’t resist a spooky story, even though there may be many of them throughout their career. Sometimes you may get put into a situation where you are taking on a higher responsibility. It doesn’t sound too bad, but in some cases one may get put into that kind of place and they may not end up being qualified. Especially if you are working in a team where they are used to certain methods being done and executed in a way where it is efficient. They may expect you to do the same thing as the person who are covering for is doing, and having high expectations on you can be quite terrifying if you are brand new.

 

e52572d331528e9dbcfba78277c7dde1

Now, that may or may not happen to every tester but there are many more scary stories out there detailing’s ones journey. Nothing is worse than working on a super-strict deadline as well especially when you have to rush what you are doing with your team (that may consist of many more testers or a very few).  If you make a mistake or over look something during that small time frame you may get in trouble. Testing overall is a stressful job after all, it is the cause of many testing horror scenarios.

Either way, if one does have a bad experience or experiences during their testing career that may be worth a Halloween’s tale, it may not be a complete waste. After all people learn from their experiences and use that knowledge to make better of themselves in the future.  As scary as some stories sound, not all seem to be a complete nightmare, just a really bad work day. Though if you do want to see more frightening things testers go through just for the sake of the Halloween spirit, check out what scares testers the most.

(Source: http://www.softwaretestinghelp.com/what-scares-testers-most/)

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.

Improving Testing Skills

I read an article this week entitled “How to Write a Test Case Structured for Your Project and Your Team” (http://blog.testlio.com/how-to-write-a-test-case-structured-for-your-project-and-your-team) which at first I did not find fascinating because as Computer Science majors, most of us should already be familiar with the general structure of test cases. However, despite the initial lack of interest I gave the article a chance and skimmed through its content and it turns out that there were some interesting test case structures that I have never heard or though of before.

One in particular that caught my attention was the “Verify-using-with-to test cases”. The article outlines the type of user of this structure to be beginning testers or employees (which is basically us once we graduate!) This test style can be applied to projects or any magnitude and is mainly focused on the actual language of the tests. The reason for the naming of this structure is because it follows the 4 key words: verify, using, with, and to. Instead of going into the definition of these 4 key terms, the example used in the article is this.

Verify: Courses send to bookstore
Using: Student ID, “Look up books”
With: Student is registered in at least one course
To: Show student courses list in student bookstore

After reading the article and going over the examples provided, I did find this particular test structure to be not only useful, but pretty easy to use so it’s something I look forward to using the next time I test!

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.

SCRUM (Week 6)

Scrum sounds more like a candy bar than an Agile software development framework, but let’s see what happens.

First Why is it called Scrum?

When Jeff Sutherland created the scrum process in 1993, he borrowed the term “scrum” from an analogy put forth in a 1986 study by Takeuchi and Nonaka, published in the Harvard Business Review. In that study, Takeuchi and Nonaka compare high-performing, cross-functional teams to the scrum formation used by Rugby teams.

How does it start?

The Product owner creates a product backlog. This back log is a prioritized wish list of all the things that he wants in the product.

Sprint Planning

Your team starts planing the sprint. This is when you take the ideas from the product back log and starts thinking and discussing how this part will be accomplished and how long it will take.

Sprint

The sprint is when the team works on the the part they decide on during planing. Usually take 2 to 4 weeks. Every day there is a meeting called a Daily Scrum. This is mainly to assess progress and make necessary adjustments. One project member is assigned as the ScrumMaster. The purpose of the scrum master is to keep everything moving smoothly and sometimes move anything blocking the way of the team.

Sprint Review

The sprint ends with a review of the product.

Scrum Retrospective

After the review of the product there is a retrospective time allotted to discuss the good, the bad, and the ugly. When done with a sprint another chunk of the product backlog is chosen and the next sprint begins.

Scrum is the idea of working in shorter increments to complete a much larger task. This can be applied to all tasks large and small. It can defiantly be helpful when you are dealing with a huge project that could potentially take months.

If you would like to know more click here, here, or here.

From the blog CS@Worcester – Conundrums In Computing by patrickgrahamblog and used with permission of the author. All other rights reserved by the author.

Automatic Vs Manual (Week 5)

(Picture was taken from a google search url here )

Scanning through the blog posts on the Ministry of testing I came across an interesting post title Evolution is hard – Testing is Evolving. I read a post about how testing is evolving from Manual to Automatic and if this trend will continue to eliminate the need for testers. This blog led me to a blog post discussing pros and cons of both (oddly enough the post has the same name as this one. I promise that was a coincident) First post here. Second post here. This post will try to sum up these two posts. I really suggest you read both post because they were very informative.

There are some out there who believe that automated testing will completely take over manual testing. This is just plain nonsense. The need for manual testers is still there because everything cannot be automated “yet”. The job titles have changed and moved on like the first blog post says “they Evolved” Moved on to be more than just manual testers to specialize more into things like Data Analysts, Performance Analyst, Security Analyst, Automation Specialist, and Technical Analysts.

The second blog post details the pros and cons of manual vs automated testing. To summarize this post i will say this. Automation stands to deal with repetitions and annoyances more so than to completely consume manual testing all together. The process of automation helps more people to focus and specialize into the areas of software development that need the help. Like automation in factories, it might start to take some jobs but it is already proving to be a benefit.

From the blog CS@Worcester – Conundrums In Computing by patrickgrahamblog and used with permission of the author. All other rights reserved by the author.

Buddy System (Week 4)

Chronicles of Testing posted an interesting article on pair testing on October 27, 2016. Jyothi Rangaiah elaborates on how pair testing has helped her as a software tester.

Pair Testing is a technique where two team members work on the same build on the same machine. One team member works with the mouse and keyboard and the other takes notes and makes scenarios.(From Midfiretesting blog)

Jyothi Rangaiah  states that pair testing is for everyone testers and non testers alike. This is because pair testing is for anyone who wants to learn about testing. Pair testing is also for anyone who wants to get help with testing. Pair testing is also for anyone who wants to share their ideas. She states that pair testing is a good experience for management and coders to analyze a problem together.

When pair testing the result is almost always a combination of both participants and turns out better than the effort of one tester. There are obvious faults in pair testing though. Some of these faults are if the pair do not get along or if the test only requires one person to work on it.

To find out more check out both the blogs listed in this post.

From the blog CS@Worcester – Conundrums In Computing by patrickgrahamblog and used with permission of the author. All other rights reserved by the author.

Unit Testing with Mock Objects (Week 6)

This article is posted by IBM and explains how the Mock Object can be used. In this article we will find some of the benefits of using Mock Objects for writing Unit tests for objects that act as mediators. Unit testing has become widely accepted for software development. When you write an object you must also provide an automated test class containing methods that put the object through its paces, calling its various public methods with various parameters and making sure that the values returned are appropriate.When we’re dealing with simple data or service objects, writing unit tests is straightforward. However, many objects rely on other objects or layers of infrastructure. When it comes to testing these objects, it is often expensive, impractical, or inefficient to instantiate these collaborators. For example, to unit test an object that uses a database, it may be burdensome to install, configure, and seed a local copy of the database, run your tests, then tear the local database down again.A mock object conforms to the interface of the real object, but has just enough code to fool the tested object and track its behavior. For example, a database connection for a particular unit test might record the query while always returning the same hardwired result. As long as the class being tested behaves as expected, it won’t notice the difference, and the unit test can check that the proper query was emitted.

Here are some of the common coding style for testing with mock objects:

  • Create instances of mock objects
  • Set state and expectations in the mock objects
  • Invoke domain code with mock objects as parameters
  • Verify consistency in the mock objects

Citation
https://www.ibm.com/developerworks/library/j-mocktest/


From the blog Table of Code by Andon S and used with permission of the author. All other rights reserved by the author.

Unit Testing with Mock Objects (Week 6)

This article is posted by IBM and explains how the Mock Object can be used. In this article we will find some of the benefits of using Mock Objects for writing Unit tests for objects that act as mediators. Unit testing has become widely accepted for software development. When you write an object you must also provide an automated test class containing methods that put the object through its paces, calling its various public methods with various parameters and making sure that the values returned are appropriate.When we’re dealing with simple data or service objects, writing unit tests is straightforward. However, many objects rely on other objects or layers of infrastructure. When it comes to testing these objects, it is often expensive, impractical, or inefficient to instantiate these collaborators. For example, to unit test an object that uses a database, it may be burdensome to install, configure, and seed a local copy of the database, run your tests, then tear the local database down again.A mock object conforms to the interface of the real object, but has just enough code to fool the tested object and track its behavior. For example, a database connection for a particular unit test might record the query while always returning the same hardwired result. As long as the class being tested behaves as expected, it won’t notice the difference, and the unit test can check that the proper query was emitted.

Here are some of the common coding style for testing with mock objects:

  • Create instances of mock objects
  • Set state and expectations in the mock objects
  • Invoke domain code with mock objects as parameters
  • Verify consistency in the mock objects

Citation
https://www.ibm.com/developerworks/library/j-mocktest/


From the blog Table of Code by Andon S and used with permission of the author. All other rights reserved by the author.

Unit Testing with Mock Objects (Week 6)

This article is posted by IBM and explains how the Mock Object can be used. In this article we will find some of the benefits of using Mock Objects for writing Unit tests for objects that act as mediators. Unit testing has become widely accepted for software development. When you write an object you must also provide an automated test class containing methods that put the object through its paces, calling its various public methods with various parameters and making sure that the values returned are appropriate.When we’re dealing with simple data or service objects, writing unit tests is straightforward. However, many objects rely on other objects or layers of infrastructure. When it comes to testing these objects, it is often expensive, impractical, or inefficient to instantiate these collaborators. For example, to unit test an object that uses a database, it may be burdensome to install, configure, and seed a local copy of the database, run your tests, then tear the local database down again.A mock object conforms to the interface of the real object, but has just enough code to fool the tested object and track its behavior. For example, a database connection for a particular unit test might record the query while always returning the same hardwired result. As long as the class being tested behaves as expected, it won’t notice the difference, and the unit test can check that the proper query was emitted.

Here are some of the common coding style for testing with mock objects:

  • Create instances of mock objects
  • Set state and expectations in the mock objects
  • Invoke domain code with mock objects as parameters
  • Verify consistency in the mock objects

Citation
https://www.ibm.com/developerworks/library/j-mocktest/


From the blog Table of Code by Andon S and used with permission of the author. All other rights reserved by the author.

Unit Testing with Mock Objects (Week 6)

This article is posted by IBM and explains how the Mock Object can be used. In this article we will find some of the benefits of using Mock Objects for writing Unit tests for objects that act as mediators. Unit testing has become widely accepted for software development. When you write an object you must also provide an automated test class containing methods that put the object through its paces, calling its various public methods with various parameters and making sure that the values returned are appropriate.When we’re dealing with simple data or service objects, writing unit tests is straightforward. However, many objects rely on other objects or layers of infrastructure. When it comes to testing these objects, it is often expensive, impractical, or inefficient to instantiate these collaborators. For example, to unit test an object that uses a database, it may be burdensome to install, configure, and seed a local copy of the database, run your tests, then tear the local database down again.A mock object conforms to the interface of the real object, but has just enough code to fool the tested object and track its behavior. For example, a database connection for a particular unit test might record the query while always returning the same hardwired result. As long as the class being tested behaves as expected, it won’t notice the difference, and the unit test can check that the proper query was emitted.

Here are some of the common coding style for testing with mock objects:

  • Create instances of mock objects
  • Set state and expectations in the mock objects
  • Invoke domain code with mock objects as parameters
  • Verify consistency in the mock objects

Citation
https://www.ibm.com/developerworks/library/j-mocktest/


From the blog Table of Code by Andon S and used with permission of the author. All other rights reserved by the author.

Unit Testing with Mock Objects (Week 6)

This article is posted by IBM and explains how the Mock Object can be used. In this article we will find some of the benefits of using Mock Objects for writing Unit tests for objects that act as mediators. Unit testing has become widely accepted for software development. When you write an object you must also provide an automated test class containing methods that put the object through its paces, calling its various public methods with various parameters and making sure that the values returned are appropriate.When we’re dealing with simple data or service objects, writing unit tests is straightforward. However, many objects rely on other objects or layers of infrastructure. When it comes to testing these objects, it is often expensive, impractical, or inefficient to instantiate these collaborators. For example, to unit test an object that uses a database, it may be burdensome to install, configure, and seed a local copy of the database, run your tests, then tear the local database down again.A mock object conforms to the interface of the real object, but has just enough code to fool the tested object and track its behavior. For example, a database connection for a particular unit test might record the query while always returning the same hardwired result. As long as the class being tested behaves as expected, it won’t notice the difference, and the unit test can check that the proper query was emitted.

Here are some of the common coding style for testing with mock objects:

  • Create instances of mock objects
  • Set state and expectations in the mock objects
  • Invoke domain code with mock objects as parameters
  • Verify consistency in the mock objects

Citation
https://www.ibm.com/developerworks/library/j-mocktest/


From the blog Table of Code by Andon S and used with permission of the author. All other rights reserved by the author.