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

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

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

he icon   en icon

  • The profile page is not available for guests

בכדי לכתוב בפורום יש להרשם או להתחבר - ההרשמה/כניסה מתבצעת מכותרת האתר.  

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

  • The Ethical Mandate for Mistake Specialists

    The Ethical Mandate for Mistake Specialists In my post Forgetting How to Test, I said “we are at a time where forgetting how to test is not just a technical dilemma, but an ethical and moral dilemma.” I still believe that. Here I’ll try to show a bit of how test thinking should lead us inexorably to that idea. This post will be somewhat in line with my “Testing is Like…” concept. I also think this post will serve as yet another example of what I talked about when I framed the question-as-statememt “So, you want to be a tester?” When you want to be a software tester, you operate in a world where it feels like there must be some key on the keyboard like the above. This is because we seem to be awash in blunders, oversights, and errors — essentially mistakes. Testing is Like Thermodynamics In thermodynamics, you have a system of some sort that has a boundary. There are inputs and there are outputs. That’s pretty much what we deal with in testing all the time. But that’s a simplistic enough analogy that it’s borderline useless. Yet in his book Einstein’s Fridge: How the Difference Between Hot and Cold Explains the Universe, Paul Sen says: “Thermodynamics is a dreadful name for what is arguably the most useful and universal scientific theory ever conceived.” His point being that the word seems to suggest a very narrow area of applicability, usually associated only with heat. But, as correctly noted, thermodynamics is “more broadly a[…]

    5.12.2021 | 2:29 קרא עוד...
  • How to approach a new automation task

    How to approach a new automation task Sometimes, (test) automation professionals are approached with a completely new task for automation. In this article, I try to give you a guideline and some questions to ask when this happens. Understand the problem The very first step to approach such a task is to thoroughly understand the problem to be solved. This typically means getting feedback from the stakeholders and users who have a pain point that can potentially be solved through automation. It also involves talking to teams who might have had this issue before since there might be some inspiration or even a complete solution that fits the problem scope. Thoughts on reinventing the wheel Even if there is already an existing solution, it is necessary to assess if it really fits the problem at hand. It might be beneficial to come up with another custom way that is better suited. This decision has more factors such as How much time do we have to develop something from scratch? What is the cost of maintenance of our solution? Is it a problem that will not exist anymore in the future (so the solution does not have to be permanent)? How well documented is the existing solution? How many maintainers does the existing solution have? If the solution under investigation is open source (or "inner source" in case of company internal development), another approach would be contributing to that existing codebase instead. Compatibility If you decide to come up with an individual solution, it is necessary to start[…]

    5.12.2021 | 11:22 קרא עוד...
  • (clj 7) Programming to abstractions with sequence functions

    Looking at my progress so far, I realized it's time re-evaluate this whole learning Clojure-thing. After looking through the table of contents of "Clojure for the Brave and True" and giving it some thought, I decided to make two changes to how I'll proceed: I will start writing shorter posts and write them more often. My goal is to finish "Part II: Language Fundamentals". I don't have to do "Part III: Advanced Topics". Completing Part II will still take quite some work. I've worked through the two first sections of chapter 4 (5 sections left in that chapter) and Part II goes up to chapter 8. So no time to waste: let's take a look at sequence functions and programming to abstractions. Read more… (7 min remaining to read)

    5.12.2021 | 6:40 קרא עוד...


  • מבט מערכתי לבודקים – Systems Thinking
    מבט מערכתי לבודקים – Systems Thinking מבט מערכתי לבודקים – Systems Thinking התכונה או מערכת אותה אנו בודקים - אינה מנותקת משאר העולם, תיקון בנקודה אחת – עשוי להשפיע ולפגוע בנקודות אחרות, ולכן על הבודק להכיר את המערכת והקשרים בין חלקיה. כמו…
    קרא עוד...
  • טיפ - עבודת בודקים בצמד עם המפתח
    טיפ - עבודת בודקים בצמד עם המפתח  עבודת בודקים בצמד עם המפתח "עבודה בצמד עם המפתח" – לעבודה בצמדים יתרונות רבים אך לעיתים היא נזנחת בשל "העלות הכפולה". בשנים האחרונות עם עליית שיטות אג'יליות ו- Extreme Programming צורת עבודה זו יותר נפוצה. כששני…
    קרא עוד...
לרשימה המלאה >>