Skip to main content

Many problems with one button



I admire the complexity which can emerge from elementary designs. Especially in the problem space.

 One example speaks for itself, the 'On/off app':
- an webapp consisting only from one button which can either turn 'things' on or off ('Picture 1' is an aproximate illustration of both visual states of the app)
- 'things' are marketing campaigns, some more complex processes to send particular marketing messages under particular conditions to particular customers (details of such don't matter in this context)

Picture 1
source: https://www.vecteezy.com/vector-art/88994-on-and-off-chrome-buttons




Even when my team was highly qualified in software development, under the fog of communication  and implicit expectations that we missed, we discovered the following problems with the implementation:
  •  Wrong template
    • The template which we used in the test environment was not meant for production, the impact was low - only a few business users saw the word 'test', but it taught us a lesson
  • Wrong business logic
    • This one was tricky, while the button should turn everything on or everything off, we didn't have the information about the production data - some marketing campaigns in production were off for long period of time. In other words the new requirement was "turn off everything what is on, but when I click you again, you turn on only those campaigns which you turned off"
    • This brought us to the realisation that we need the requirements explicit, so while writing them own, I discovered curious situations which can occur from such simple design, including pressing it from different sessions/users. As far I remember there were around 10 different scenarios which have been documented
  • Initial account sync
    • This was another blind spot, bound to the first launch of the app - the items which needed to be migrated to our DB. We found out there were several millions of them, which naturally caused our app to freeze. Althought this was fixed quite quickly, I will always remember to think about this aspect in future

Lesson learned

Don't be comforted with the straightforward simplicity of the system in front of you, the complexity can be much deeper than you realize. Like a famous clothing brand says: "Never stop exploring"
Labels:

Comments

Post a Comment

Popular posts from this blog

When to start automation?

If you are asking this as a tester, you probably asking too late. Automation is something that can save you some portion of your work (understand resources for your client) and i rarely found cases of testing work that did not need at least some portion of automation. I know that it is rarely understood that automation is something to be developed & maintained and if you cover enough of the application, you do not need any more regression - well i do not think that somebody has done an automation regression suite that if fully reliable (i am not speaking about maintaining this code - which is another topic). There can be always a bug (or quality issue) that slips through, even when you scripts go through the afflicted part. I understand that many testers have no development background or skills, but i doubt the developers that could help you are far away. I am not assuming that they can do the scripts for you.... However if they understand what you need, they can say how e...
4 comments
Read more

Testing impact on security

... or the impact when testing is lacking? Security breaches , hacks , exploits , major ransomware attacks - their frequency seem to increase recently. These can result in financial, credibility and data loss, and increasingly the endangerment of human lives. I don't want to propose that testing will always prevent these situations. There were probably testers present (and I'm sure often also security testers) when such systems were created. I think that there was simply a general lack of risk-awareness on these projects. There are many tools and techniques from  a pure technical point of view to harden the software in security context. Some of them have automated scans which crawl through your website and might discover the low hanging fruits of security weaknesses ( ZAP , Burpsuite ...), without much technical knowledge from the person operating it. The more important aspect is however the mindset with which you approach the product. The tester is often the f...
Post a Comment
Read more

RST Explored - My experience

My experience report from my recent RST Class I attended the RST class after a while, wanting to refresh my knowledge about the RST view on testing. It was a 4-day event, each day 3 Sessions, approx 4hour/day. My general impression was that it enriched and refreshed my understanding of testing.   Each of the four days had an central theme Day 1: "It is possible to test everything?" Day2: "When to stop testing? How to test from specifications." Day3: "Product coverage outline. Complexity of the system" Day4: "Risk analysis and coverage"   Going deeper into the topics of each day would be impossible without spoilers, I will therefore rather focus on my impressions and what this training has brought me. The way Michael was guiding us through the class was very engaging, although we usually started with a short lecture, questions and remarks were encouraged from start and we had an shared review after each exercise - students explaining their work,...
Post a Comment
Read more