LOGIN
התחברות או הרשמה
להמשך הרשמה ידנית – לחץ על כפתור ההרשמה, להרשמה/כניסה מהירה בעזרת חשבון רשת חברתית – לחץ על הלוגו בכותרת
בכדי להוסיף פוסט בבלוג יש להרשם או להתחבר - ההרשמה/כניסה מתבצעת מכותרת האתר.
Have you ever found yourself working on an automated test suite and wondered if it's worth the effort? It's probably a typical thought that goes through the minds of every developer and tester working on test automation. Even in all of my years of building and maintaining automated tests, I admittedly find myself thinking this way occasionally, wondering if there's a better use of time elsewhere on the project.Whenever I notice teams of developers and testers not putting any emphasis on test automation, it's usually because there's a level of uncertainty in the effectiveness of automated tests. The team might think it would help their work but can't or won't dedicate some time to know for sure. Worse yet, some teams believe that test automation is an added burden to the software development and testing process with little to no reward. These developers and testers proceed with the belief that they can deliver quality work faster by skipping these types of tests.Even teams with a solid test automation strategy in their workflow have some reservations about the effectiveness of their test suite. They can't figure out how to gauge the success of their testing work and try to find ways to measure it, like counting the number of automated test cases or keeping track of code coverage. While these seem like good metrics, they're not as valuable as you might think.If you're in a team trying to determine if your test automation work is worth the effort, how can you[…]
SPRING IS HERE! Well, not really. Well, according to my window it looks like it, but the calendar says otherwise. But the recording of the Tips for Spring Testing webinar is here. In fact, it’s just below. Check it out! Oh, and if you’re interested in some training on these topics, let me know! The post “Spring Testing Tips” Webinar Recording first appeared on Everyday Unit Testing.
30.11.2021 | 2:27 קרא עוד...
We want to find bugs as early as possible so that the cost of fixing them is as little as possible.
The earlier a bug is found the cheaper it is to fix. If a bug is found and fixed in a specification before any code is written then it costs very little to fix. If a bug is found during development then it costs some development time to fix it. If a bug is found in production and fixed then the cost to fix it includes some development time, some customer service time and its effect on customers. A lean perspective expresses this in another way as lean is about reducing waste and improving the flow of work. Bugs are waste so finding bugs early is lean because it reduces waste, and so improves the flow of work.
The value of testing as early as possible was highlighted by Tom Gilb when I heard him speak about ‘Lean QA’ a few years ago. He spoke about how it is best to find issues as early as possible in development.
The advantages are clear in theory and it is helpful to be able to give examples. Tom Gilb spoke about inspecting specifications for software before code is written as an example of early testing and showed how many issues can be identified by inspecting the specifications. One way for testers to help with inspecting specifications is to review requirements with a developer before they start work as this may identify[…]
במסגרת עבודת הבדיקות - אל תפסיקו לשאול שאלות... אחרי שקראתם את הרקע לנושא הנבדק, פנו למהנדסי המערכת, והבהירו עמם נקודות שאינן ברורות, גם אם נראה לכם כי הבנתם הכל, השתדלו לשאול שאלות פתוחות - לעולם אינכם…
איך לכתוב בדיקות שישמשו אתכם גם בעתיד? אל תסתפקו בכתיבה יבשה של צעדי הבדיקה ותוצאות צפויות – סגנון כתיבה כזה יביא אתכם למצב בו בעוד מס' חודשים אתם או מישהו אחר שאמור לבצע או לשכתב את…
