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

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

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

he icon   en icon

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


sali weizman קבוצות

לא נמצאו קבוצות.

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

  • Meetup And Learn, Antipatterns, Loads and Tester Salaries

    TL;DR This post is about my learning experience on Testival #56 meetup. This time we gathered in the ground floor lobby in HUB385. The host and sponsor of this meetup...

    22.01.2020 | 12:00 קרא עוד...
  • Five Blogs – 22 January 2020

    The (best) five blogs I read today. Check them out. Expanding my Horizons – The End of QA As We Know It Written by: Ursula Beiersdorf What is a Unit Test? Part 2: classical vs. London schools Written by: Vladimir Khorikov Would Heu-risk it? Part 10: Forever and never. Written by: Lena Pejgan Wiberg 4 Words to Help You Build a Powerful Team Written by: David Dye Unknowing Leadership Written by: Steve Keating Quote of the day: “Take responsibility of your own happiness; never put it in other people’s hands.” -Roy T. Bennett You can follow this page on Twitter

    21.01.2020 | 11:14 קרא עוד...
  • Why using branches is good for your tests

    Why using branches is good for your tests Branches are beautiful, on trees. Branches in the code are not what many testers like to work with. The whole branching process appears to be very cumbersome: creating the branch, keeping it up to date with the main branch, deleting it once the work is done, these all seem to take a lot of time and to not be the most fun activities. However, there are some situations when branching really needs to be considered. When you are working on sprint tasks that require you to create new code, maybe you don’t want or need to branch. New classes can be easily added to the main branch, without disrupting code that other people write in the same project, as long as everybody is working on different tasks/classes/methods. However, adding the new code to the code repository needs to be done in such a way that it does not break the code project and allows it to compile and run successfully. Incomplete code, that does not even compile locally, should not be pushed to the code repository. The newly written test code should also not break the continuous delivery pipeline runs. This means that tests committed to the main branch are complete and need to pass (as long as there is no bug in the functionality they are testing). Otherwise, if the commit is not a fully functional and correct test, the pipeline will stop when the committed test is run, and the CI process is broken, even though there is[…]

    21.01.2020 | 10:42 קרא עוד...


  • נתקעת ללא רעיון? - קבל רעיון רנדומלי
    נתקעת ללא רעיון? - קבל רעיון רנדומלי נתקעת ללא רעיון? - קבל רעיון רנדומלי מ- Oblique Strategies Trick by Michael Bolton רקע לנושא: Oblique Strategies © 1975, 1978, and 1979 Brian Eno/Peter Schmidt This web page © 1997 Gregory Taylor (כבודקים נוכל לפתח רשימות…
    קרא עוד...
  • מבט טרי מביא באגים טריים
    מבט טרי מביא באגים טריים מבט טרי מביא באגים טריים באופן טבעי אנו כבודקים מתמחים בעבודה עם המוצר שאותו אנו בודקים, בהרבה מקרים זהו יתרון (אנו יכולים לזהות בעיות, לעבוד מהר יותר וכן הלאה), אך לעיתים זהו חיסרון – אנו מפתחים…
    קרא עוד...
לרשימה המלאה >>