Twitter | Search | |
Jesper
Manages testing of all kinds of IT projects at . Non-commercial. Topics: testing, LEGO, Star Wars, RPA, business strategy. him/his/cis.
8,977
Tweets
493
Following
1,152
Followers
Tweets
Jesper 3h
one day at the time. I can only imagine how hard it is. Love to you, and Kristian
Reply Retweet Like
Jesper 12h
Replying to @andersdinsen
It depends ;)
Reply Retweet Like
Jesper 12h
Replying to @andersdinsen
Reply Retweet Like
Jesper 22h
Testing Challenge of the day: It has to work as before, just different... Says the business when implementing a new platform. Learn how to develop test strategies for different contexts at
Reply Retweet Like
Jesper Aug 20
Could another label for "genesis" on the evolution curve be "1 off"/"one time" and then evolute into repeatable patterns? That would elaborate the cheat sheet for a practice I'm looking at.
Reply Retweet Like
Jesper Aug 19
Testing Challenge of the Day: To challenge or to confirm requirements - given the context and time box. ie: should we add test automation for negative scenarios on the flows through a standard application?
Reply Retweet Like
Jesper retweeted
𝑫𝒂𝒏 𝑨𝒔𝒉𝒃𝒚 Aug 19
TESTERS! Anything you spend your time doing that adds value, make it visible! It'll help the developers within the team that you are embedded in to see the value that you are bringing to the team. Don't keep it a mystery to them.
Reply Retweet Like
Jesper Aug 19
To get someone to do something - someone has to CARE about it Thank you for reminding me Lanette
Reply Retweet Like
Jesper Aug 15
Replying to @RudolfGroetz
Thank you Rudolf :) same Challenge just years later 🤓
Reply Retweet Like
Jesper Aug 15
Testing Challenge of the Day : Our test automation _can_ cover all the combinations in the solution's product catalog (order entry). But do we want to test everything every day? The current catalog is test data, so probably not (yet)
Reply Retweet Like
Jesper retweeted
João Proença Aug 14
The concept of “done” can be connected to the business outcomes of this slide. at . I’ve actually seen companies where a feature only gets accepted and “done” once it has clearly demonstrated in production that it’s generating more revenue!
Reply Retweet Like
Jesper retweeted
lisacrispin Aug 14
We think we're scientists, but we rely on gut instinct, scar tissue from past service outages, and pattern matching. asks, how many of your last 20 major service outages did you fully understand? Did any fix themselves and leave you wondering?
Reply Retweet Like
Jesper Aug 14
Replying to @qahiccupps
uuuuh, would love to apply some SBTM on this. great idea!
Reply Retweet Like
Jesper Aug 14
Replying to @qahiccupps
the team has been running 20 years, all the know-how is in their heads, not codified. there are currently no acceptance criteria on the stories 🙄 we want to know what is tested - as it is being tested. what they did test could be a start tnx!
Reply Retweet Like
Jesper Aug 14
Replying to @J_teapot
step 1: to know what the scope of testing is .. at all step 2: to reuse step 3: to repeat and perhaps automate
Reply Retweet Like
Jesper Aug 14
Testing challenge of the day: How do we get experienced subject matter experts to see a value in writing down what they will do of testing. .. in any form really
Reply Retweet Like
Jesper retweeted
Kristen Belcher Aug 12
I never met , but this quote is one of my favorites: "Things are the way they are because they got that way."
Reply Retweet Like
Jesper Aug 13
and bring cake :D
Reply Retweet Like
Jesper Aug 13
ProTip from the Community of Practice AMA on and : 1) don't call it meetings :D 2) alternate and vary the timeslot
Reply Retweet Like
Jesper Aug 13
A moo from the Far Side!
Reply Retweet Like