We use cookies to ensure that we give you the best experience about vital software issues 'n stuff. A cookie is a small text file containing information that a website transfers to your computer's hard disk for record-keeping purposes and allows us to analyze our site traffic patterns. It does not contain chocolate chips, you cannot eat it and there is no special hidden jar. If that's still okay for you, and you want to continue to use our website, you can close this message now (don't forget to read our Data Privacy Notice). Otherwise you gotta leave now :-( Close

Leave a Comment

Posted on February 15, 2021

The Little Tester #135

by

These are the made up stories of a team working in an Agile environment. Their daily struggles and successes are presented in a comic/parody/satirical way. Click on the image to see it in full size.

The team members are:

  • Little, the main character. The team’s tester.
  • Coffee, the team’s Java developer.
  • Mr. Fancy, the team’s UI developer.
  • Senor, the Senior Developer of the team.
  • Kitty, the Scrum Master.
  • Glasses, the Business Analyst.
  • And the manager.

Disclaimer

  • This is a work of fiction. Names, characters, businesses, places, events, situations presented are either the products of the author’s imagination or used in a fictitious manner. Any resemblance to actual persons or events is purely coincidental.
  • The sole purpose of this comic strip is to be humorous.
  • The drawings are made by hand on paper, by means of pencils and fine liners, except for the outline, by the author. Hence their imperfection.
(Source: imalittletester)

Cyndi wants you to know: "The formatting of this article went shite due to causeless use of HTML <blockquote> tags in the original post." 🤷‍♀️

Leave a Comment

Posted on February 10, 2021

It gives him the answer

by

The omniscient corny horn pours out the following words of wisdom:
Chuck Norris never searches online, he stares at his computer and it gives him the answer.

Leave a Comment

Posted on February 8, 2021

The Little Tester #134

by

These are the made up stories of a team working in an Agile environment. Their daily struggles and successes are presented in a comic/parody/satirical way. Click on the image to see it in full size.

The team members are:

  • Little, the main character. The team’s tester.
  • Coffee, the team’s Java developer.
  • Mr. Fancy, the team’s UI developer.
  • Senor, the Senior Developer of the team.
  • Kitty, the Scrum Master.
  • Glasses, the Business Analyst.
  • And the manager.

Disclaimer

  • This is a work of fiction. Names, characters, businesses, places, events, situations presented are either the products of the author’s imagination or used in a fictitious manner. Any resemblance to actual persons or events is purely coincidental.
  • The sole purpose of this comic strip is to be humorous.
  • The drawings are made by hand on paper, by means of pencils and fine liners, except for the outline, by the author. Hence their imperfection.
(Source: imalittletester)

Cyndi wants you to know: "The formatting of this article went shite due to causeless use of HTML <blockquote> tags in the original post." 🤷‍♀️

Leave a Comment

Posted on February 8, 2021

The Little Tester #134

by

These are the made up stories of a team working in an Agile environment. Their daily struggles and successes are presented in a comic/parody/satirical way. Click on the image to see it in full size.

The team members are:

  • Little, the main character. The team’s tester.
  • Coffee, the team’s Java developer.
  • Mr. Fancy, the team’s UI developer.
  • Senor, the Senior Developer of the team.
  • Kitty, the Scrum Master.
  • Glasses, the Business Analyst.
  • And the manager.

Disclaimer

  • This is a work of fiction. Names, characters, businesses, places, events, situations presented are either the products of the author’s imagination or used in a fictitious manner. Any resemblance to actual persons or events is purely coincidental.
  • The sole purpose of this comic strip is to be humorous.
  • The drawings are made by hand on paper, by means of pencils and fine liners, except for the outline, by the author. Hence their imperfection.
(Source: imalittletester)

Cyndi wants you to know: "The formatting of this article went shite due to causeless use of HTML <blockquote> tags in the original post." 🤷‍♀️

Leave a Comment

Posted on February 1, 2021

The other slide

by

The omniscient corny horn pours out the following words of wisdom:
Q: Why did the PowerPoint presentation cross the road?
A: To get to the other slide.

Leave a Comment

Posted on February 1, 2021

A really good UDP joke

by

The omniscient corny horn pours out the following words of wisdom:
I’ve got a really good UDP joke to tell you, but I don’t know if you’ll get it.

Leave a Comment

Posted on February 1, 2021

The Little Tester #133

by

These are the made up stories of a team working in an Agile environment. Their daily struggles and successes are presented in a comic/parody/satirical way. Click on the image to see it in full size.

The team members are:

  • Little, the main character. The team’s tester.
  • Coffee, the team’s Java developer.
  • Mr. Fancy, the team’s UI developer.
  • Senor, the Senior Developer of the team.
  • Kitty, the Scrum Master.
  • Glasses, the Business Analyst.
  • And the manager.

Disclaimer

  • This is a work of fiction. Names, characters, businesses, places, events, situations presented are either the products of the author’s imagination or used in a fictitious manner. Any resemblance to actual persons or events is purely coincidental.
  • The sole purpose of this comic strip is to be humorous.
  • The drawings are made by hand on paper, by means of pencils and fine liners, except for the outline, by the author. Hence their imperfection.
(Source: imalittletester)

Cyndi wants you to know: "The formatting of this article went shite due to causeless use of HTML <blockquote> tags in the original post." 🤷‍♀️

Leave a Comment

Posted on January 27, 2021

Interpreting the Regression Test Activity Graph

by

We just completed a 1.5 week intensive manual regression test phase where we executed almost the complete set of all (several hundreds) test cases. We are in a lucky situation. Our documented test cases represent nearly 100% of all implemented features. If we achieve a 70-80% test coverage, then we get a real good picture of the overall quality of the product increment. That means, aside from the many automated tests, it's worth from time to time, doing some manual end-to-end regression testing.

While tracking the progress using a cloud based test case management tool, I was looking at the activity graph and it made me smile. It's exactly what I expected.


 
At the beginning, testers focus executing those test cases that are well documented, having clear instructions and which rely on previously well prepared test data. I mean, objects that are in specific states where testers can execute just the transition from one state to the next and not worry about the laborious setup steps.
 
Then, testers switch to more complex test cases which take a little more time to understand and test.  This is when the progress curve reaches the peak and progress starts to slow down.
 
Of course, we also find anomalies. Bugs can slow you down because analyzing and understanding where and when defects were introduced takes additional time. After a few days, the first bugfixes are delivered, too. Developers require your attention to test their fixes. This interrupts testers from working on their suite. The rate of passed tests is decreasing, but still decreasing in a constant and expected way.
 
In parallel, developers are working already on the next generation of the product, meaning, their user stories get shipped and require testing too. The tester's brain is now busy with a lot of context switching; clearly more than at the beginning of the sprint.
 
Now that we are more than half way through, we switch to the monster test cases. I call them like that because they do not consist of simple steps, they contain several tests expressed in tables of inputs and expected outputs. That's why I think it's nonense to talk about the number of test cases. A test case can be atomic and executed in seconds, yet another test case can keep you busy for half an hour and more.

Some of the test cases may be poorly documented and require maintenance or correction. Some test cases require the help of a domain expert. The additional information gained should be documented in the test suite, so we don't have the same questions next time. These are all activities running in parallel.

Last but not least, weekend is getting closer. The first enthusiasm is gone, you're starting to get bored.
You hear music from your neighbour. The caféteria gets louder. The sound of clinking glasses reaches your desk. It's time for a break, time to reboot your brain. TGIF! And now it's weekend time!
Never have testers work on a weekend, unless they can't live without.
 
And then, Monday is back! It's time for another final boost and time to say thank you. Great progress.
We made it Yogi! ....and I like that graph.
 
 
 

 


(Source: Simply the Test)

Leave a Comment

Posted on January 25, 2021

The Little Tester #132

by

These are the made up stories of a team working in an Agile environment. Their daily struggles and successes are presented in a comic/parody/satirical way. Click on the image to see it in full size.

The team members are:

  • Little, the main character. The team’s tester.
  • Coffee, the team’s Java developer.
  • Mr. Fancy, the team’s UI developer.
  • Senor, the Senior Developer of the team.
  • Kitty, the Scrum Master.
  • Glasses, the Business Analyst.
  • And the manager.

Disclaimer

  • This is a work of fiction. Names, characters, businesses, places, events, situations presented are either the products of the author’s imagination or used in a fictitious manner. Any resemblance to actual persons or events is purely coincidental.
  • The sole purpose of this comic strip is to be humorous.
  • The drawings are made by hand on paper, by means of pencils and fine liners, except for the outline, by the author. Hence their imperfection.
(Source: imalittletester)

Cyndi wants you to know: "The formatting of this article went shite due to causeless use of HTML <blockquote> tags in the original post." 🤷‍♀️

Leave a Comment

Posted on January 21, 2021

ISTQB® Sunset dates and information regarding ISTQB® Advanced Level Test Analyst and Technical Test Analyst Syllabus 2012 (CTAL-TA-2012/CTAL-TTA-2012)

by

ISTQB® Advanced Level (CTAL) Test Analyst (TA) and Technical Test Analyst (TTA) 2012 in English will be retired as public syllabuses, including exams and training material, as of February 4th 2021 (other languages are available until 4th August 2021).

What does that mean?

This means that from February 4th 2021:

  • For English language - the 2019 syllabuses for CTAL TA and CTAL TTA will be current versions.
  • Training providers in your country/region will only be allowed to provide accredited courses, delivered in English, based on the 2019 syllabuses for CTAL TA and CTAL TTA.
  • Training in other languages may continue for the CTAL TA and CTAL TTA 2012 syllabuses until 4th August 2021.
  • CTAL TA and CTAL TTA certification exams in English will only be valid if aligned to the 2019 syllabus versions.
  • Exams in other languages are still allowed for CTAL TA and CTAL TTA 2012 until 4th August 2021.

Read the Press Release for more information.

(Source: ISTQB)

Copyright © 2025 · All Rights Reserved · Vital Software Issues 'N Stuff

90s Retro from Organic Themes · RSS Feed