he icon   en icon

התחברות או הרשמה
להמשך הרשמה ידנית – לחץ על כפתור ההרשמה, להרשמה/כניסה מהירה בעזרת חשבון רשת חברתית – לחץ על הלוגו בכותרת

אפס סיסמה - שכחתי את שם המשתמש

שם משתמש
זכור אותי

בדיקות תוכנה מישראל


חדשות מעולם הבדיקות

  • Fragile Tests vs Flaky Tests

    Some call them flaky tests. Some call them fragile tests. Or unstable. I say it’s neither, it’s the code. Nobody likes them, regardless. But here’s something interesting I heard in a conversation with one of my clients. He said: “I like calling them flaky tests, not fragile”. Why? I asked. They mean exactly the same thing. Ah, that’s true, said the developer. But it sounds different. “Fragile tests” sounds like being fragile is the intrinsic property of the tests. They are just like that, there’s nothing we can do about it, and we’ll just have to live with them like that. “Flaky tests” sounds a little different. It sounds like someone (not pointing fingers here, but you know who you are) hasn’t done enough to remove the flakiness. It is not a part of the test, it is something that clung to it, like what you’re thinking about right now. And it can (and should) be removed. In other words, “fragile tests” don’t sound like they carry responsibility, while “flaky tests” do. I liked this explanation. The responsibility for stability and consistency is there regardless of how we call it (whether it is in the code, test, or both). It’s just in one case, if you listen closely, you’ll hear the test whispering to you: “Don’t leave me like that. Fix us”. And it is our responsibility. For more a-fixing tests, and testability improvement, check out my “API Testing for developers” workshop. Because we are responsible developers, yes we are.[…]

    20.02.2024 | 1:56 קרא עוד...
  • Get insights from “The World of W. Edwards Deming” by Cecelia S. Kilian

    Get insights from “The World of W. Edwards Deming” by Cecelia S. Kilian Cecelia S. Kilian was W. Edwards Deming‘s long-term secretary. She created this book which contains her memories, and many curated documents from Deming. I read this book with the Profound Deming Book Club and it made me think about why I am interested in Deming. The details of Deming’s life are interesting, however I am interested in him because I want the same things he did. I want companies to be successful businesses by continually improving the quality of their products and services.  The most interesting chapters in the book are Deming’s notes on what he taught Japanese management in 1950 at lectures which he was invited to give by the Japanese Union of Science and Engineering. The book includes notes on his lecture at Mt. Hakone. If I understand the history of the idea I understand the idea more deeply. I found it fascinating to read in the notes of lectures from nearly 75 years ago many ideas that are used today. These points are taken from the chapters about Deming’s 1950 lectures : Building quality into a product: “You can not inspect quality into a product”. ”You must build in quality” [1] The use of control charts to analyse processes, as is done in many industries today. [1] User testing, which he describes as consumer research.” Consumer research is communication between the manufacturer and users and potential users” of the product or service”. [3] The plan-do-study-act cycle. Today the plan-do-study-act cycle describes a software development team’s iterations[4] and[…]

    20.02.2024 | 1:37 קרא עוד...
  • Beyond the Hype: Can technology sustainability really make a difference?

    In this episode, Oliver Cronk is joined by experts including Jeremy Axe, Group CTO at DS Smith, and consultants Darren Smith and Katie Davis from Scott Logic. Together, they unpack topics like the energy usage and carbon emissions of IT infrastructure, the challenges in accurately measuring sustainability, and whether claims of ‘green tech’ are substantiated or just hype. The conversation covers the nuances around operational versus embodied carbon emissions, the sustainability trade-offs involved in cloud versus on-premises hosting, and the need for transparency and standards around eco-friendly tech claims. Links from the podcast Proposed Technology Carbon Standard – open sourced by Scott Logic under a CC BY-NC-SA 4.0 licence Scott Logic blog posts on Sustainability – including the Conscientious Computing series DS Smith’s approach to sustainability Scott Logic’s approach to supporting technology sustainability Subscribe to the podcast Apple Podcasts Google Podcasts Spotify

    19.02.2024 | 9:42 קרא עוד...


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