Posted on

Automate Manual Regression Test Plan – (Testing thoughts Part 1 of N)

In this simple article, I want to share some thoughts about how to automate  a manual regression test plan . I did a simple poll where I asked :

Which tool/framework do you use to automate the execution of a full manual regression test plan to validate business scenarios ?

Before answering, you should think about the “Ice-cream testing cone”

ICECREAMCONE_TEST

Ice-cream cone : If you are testing through the User Interface (UI) them it will be slow, increasing build times. For more information please click on this article by Martin Fowler.

Ads: curso práctico de testing automático presencial y también online

From the previous image, it is clear that it is not a good idea to invest much time building a huge collection of UI Tests and here we have the results of the Poll :

Continue reading “Automate Manual Regression Test Plan – (Testing thoughts Part 1 of N)”

Posted on

Feature Toggle (Part 1 of N)

Do you have a variable flag which depending of the configuration the flag will enable/disable (toggle) to execute some lines of code of a feature.? are you tired of this approach?

This patterns was known as “Feature Toggle” which is a set of patterns which can help a team to deliver new functionality to users rapidly but safely.

“Feature Toggling” could be done with t just a variable flag but there are other better way to do it but of course it will require more time to implement it.

Working with toggle feature it will help in:

  • Adopt new technologies as part of feature toggles
  • Clean Code (if don’t use just simple variable flags)
  • Reduce Risk branch merges issues “feature branch”
  • other more things!

overview-diagram.png

Image source from this great “Feature toggling” article

“Feature Toggling” could be used when

Continue reading “Feature Toggle (Part 1 of N)”

Posted on

Application Timeout issues in the real Software World (Part 1 of N)

In a perfect Software World the application timeout issues shouldn’t happens but since the perfect Software World doesn’t exist we need to deal with the application timeouts.

Do you have only one default hard-cording value timeout for the full application? or do you have different hard-cording value for different part of the application ?

I think for the real Software World at least it will be good to be possible configure the global application timeout used in the application instead to have a default hard-cording value .

What do you think about have configurable the application timeout?

Network database concept

Imprimir

I search for this topic and I found this article about how to Planning and handling timeouts in service-oriented environments written by

Continue reading “Application Timeout issues in the real Software World (Part 1 of N)”