הרשמה     |     אודות המגזין / צור קשר      

• My first and most memorable defect!

  As test engineers, we fondly remember the defects that we found in our careers – the first one, the most memorable one, the nastiest one, and so on. Well, in my case, there have been several nasty ones, and they are countless – core dumps and such. But I fondly remember the first one and that happens to be the most memorable defect too. This also happened to be my first Software Testing project that I worked in. I was working on a C compiler as part of the development team, maintaining some modules that need to be rewritten for new requirements. A team member was working on a new casting requirement for a new data type, and another one was working on optimization of target code generated out of the DAG. As these two people didn’t have a bandwidth to test their modules with an ‘out-of-the-box’ thinking, and since they were focusing on their own individual modules and no one was looking at the product from an integration perspective, I was asked to do some ‘sanity’ checks to make sure that the modules worked fine with each other when integrated. So, I sat thinking about what would comprehensively test these two modules together. On one side, I got to test the new data type, and on the other side, I need to make sure that the output assembly is fine. I figured that the only way to do that would be to execute each and every data type along[…]

  12.08.2022 | 2:53 קרא עוד...

• The Agile Manifesto is a poor introduction to Agile

  Last week Elizabeth Zagroba asked on Twitter: If someone was completely new to working on software on an Agile team, what would you want them to read about Agile first? My first thought was: "The Agile Manifesto!" After a second thought, though, I reconsidered and replied: And I would recommend against reading the Agile Manifesto without consulting any secondary sources, except if you read it in the same way as you would visit a historical site "just to see where it all happened". As I wrote this, I could not really put my finger on why exactly I felt this way. The best I could come up with was that the Agile Manifesto is hard to understand on its own. You need some historical context and practical experience to make sense of it. Serendipity came to the rescue, though, as I'm currently reading Seeing Like a State by James C. Scott. Chapter 9 of the book focuses on the Greek concept of mētis (μῆτις) and how it relates to rules of thumb. Turns out that this explains why the Agile Manifesto is a poor introduction to Agile. Read more… (6 min remaining to read)

  12.08.2022 | 2:37 קרא עוד...

• Five Blogs – 12 August 2022

  The (best) five blogs we can read today. Check them out. Testing Strategies For Microservices Written by: Tomas Fernandez Leaps and Boundary Objects Written by: James Thomas Don’t write Conditional Logic in Tests Written by: Ethan Carlsson API Testing — Dissecting A Few Pieces Of The Developer Tools Written by: Ryan Craven Testing a PDF file with Cypress Written by: Filip Hric Quote of the day: “You taught me how to be alone. And I learned my lesson, in your absence.” -Iain Thomas You can follow this page on Twitter

  12.08.2022 | 1:40 קרא עוד...

לרשימה המלאה >>