Activity

Oleksandr Romanov profile image
Oleksandr Romanov
Senior Software Engineer in Test
He/him

14+ years in testing and engineering | Co-host at Testing Minutes podcast | Writing and podcasting about test engineering, performance, AI, blockchain, and distributed systems | Views are my own

Open To
CV Reviews
Write
Teach
Speak
Mentor
Podcasting
Review Conference Proposals
Chapter Lead
Ambassador
Member joined AI Chapter chapter image
Member joined AI Chapter chapter
This Week in Quality image
This Week in Quality
Oleksandr Romanov
Oleksandr Romanov
registered for:
This Week in Quality image
Share your week’s highlights, challenges, and lessons in quality
What's the hardest part of defining "expected behaviour" for a system that produces different output every time? image
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
What's the hardest part of defining "expected behaviour" for a system that produces different output every time? image
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
Wizard Zines: learning hard tech from comic books image
Wizard Zines: learning hard tech from comic books
Wizard Zines: learning hard tech from comic books image
Wizard Zines: learning hard tech from comic books
Oleksandr Romanov
Oleksandr Romanov
contributed:
What's the hardest part of defining "expected behaviour" for a system that produces different output every time? image
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
What's the hardest part of defining "expected behaviour" for a system that produces different output every time? image
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
What's the hardest part of defining "expected behaviour" for a system that produces different output every time? image
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
What's the hardest part of defining "expected behaviour" for a system that produces different output every time? image
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
What's the hardest part of defining "expected behaviour" for a system that produces different output every time? image
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
What's the hardest part of defining "expected behaviour" for a system that produces different output every time? image
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
Oleksandr Romanov
Oleksandr Romanov
contributed:
What's the hardest part of defining "expected behaviour" for a system that produces different output every time? image
When a system improvises like a jazz soloist, "different" stops meaning "wrong"
Metamorphic testing image
Metamorphic testing
Member joined AI Chapter chapter image
Member joined AI Chapter chapter
Member joined TWiQ — This Week in Quality chapter image
Member joined TWiQ — This Week in Quality chapter
The real ROI of experimentation image
The real ROI of experimentation
Member joined AI Chapter chapter image
Member joined AI Chapter chapter
Book Review: Full Stack Testing image
Book Review: Full Stack Testing
Book Review: Full Stack Testing image
Book Review: Full Stack Testing
Oleksandr Romanov
Oleksandr Romanov
contributed:
Oleksandr Romanov
Oleksandr Romanov
contributed:
Hot take: if you're surprised by a product behaviour, you don't understand the system enough image
Hot take: if you're surprised by a product behaviour, you don't understand the system enough
Hot, flaky, and unfinished - Testing, accessibility, and the grief we don't talk about - Ep 137 image
Hot, flaky, and unfinished - Testing, accessibility, and the grief we don't talk about - Ep 137
Hot, flaky, and unfinished - Testing, accessibility, and the grief we don't talk about - Ep 137 image
Hot, flaky, and unfinished - Testing, accessibility, and the grief we don't talk about - Ep 137
Member joined TWiQ — This Week in Quality chapter image
Member joined TWiQ — This Week in Quality chapter
Hot take: if you're surprised by a product behaviour, you don't understand the system enough image
Hot take: if you're surprised by a product behaviour, you don't understand the system enough
Hot, flaky, and unfinished - Testing, accessibility, and the grief we don't talk about - Ep 137 image
Hot, flaky, and unfinished - Testing, accessibility, and the grief we don't talk about - Ep 137
Hot, flaky, and unfinished - Testing, accessibility, and the grief we don't talk about - Ep 137 image
Hot, flaky, and unfinished - Testing, accessibility, and the grief we don't talk about - Ep 137
Member joined AI Chapter chapter image
Member joined AI Chapter chapter
Hot take: if you're surprised by a product behaviour, you don't understand the system enough image
Hot take: if you're surprised by a product behaviour, you don't understand the system enough
Hot, flaky, and unfinished - Testing, accessibility, and the grief we don't talk about - Ep 137 image
Hot, flaky, and unfinished - Testing, accessibility, and the grief we don't talk about - Ep 137
Hot, flaky, and unfinished - Testing, accessibility, and the grief we don't talk about - Ep 137 image
Hot, flaky, and unfinished - Testing, accessibility, and the grief we don't talk about - Ep 137
Hot, flaky, and unfinished - Testing, accessibility, and the grief we don't talk about - Ep 137 image
Hot, flaky, and unfinished - Testing, accessibility, and the grief we don't talk about - Ep 137
Oleksandr Romanov
Oleksandr Romanov
contributed:
Hot, flaky, and unfinished - Testing, accessibility, and the grief we don't talk about - Ep 137 image
Judy and Clare trade spicy hot takes, from notification overload and 'done > perfect' learning, to a passionate deep dive on accessibility as a moral (and business) imperative.
Thanks for joining the stage during TWiQ. image
Thanks for joining the stage during TWiQ.
Hot take: if you're surprised by a product behaviour, you don't understand the system enough image
Hot take: if you're surprised by a product behaviour, you don't understand the system enough
Hot take: if you're surprised by a product behaviour, you don't understand the system enough image
Hot take: if you're surprised by a product behaviour, you don't understand the system enough
Hot take: if you're surprised by a product behaviour, you don't understand the system enough image
Hot take: if you're surprised by a product behaviour, you don't understand the system enough
Hot take: if you're surprised by a product behaviour, you don't understand the system enough image
Hot take: if you're surprised by a product behaviour, you don't understand the system enough
Oleksandr Romanov
Oleksandr Romanov
contributed:
Hot take: if you're surprised by a product behaviour, you don't understand the system enough image
Oleksandr said: My hot take of the week: If you don't fully understand the thing you want to test and measure - you might get the results that are surprising but yet mysterious. So - first - unders...
This Week in Quality image
This Week in Quality
This Week in Quality image
This Week in Quality
Oleksandr Romanov
Oleksandr Romanov
registered for:
This Week in Quality image
Share your week’s highlights, challenges, and lessons in quality
Member joined TWiQ — This Week in Quality chapter image
Member joined TWiQ — This Week in Quality chapter
Book Review: Mastering Blockchain image
Book Review: Mastering Blockchain
Subscribe to our newsletter