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

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

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

he icon   en icon

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

ברוך הבא, אורח
שם משתמש: סיסמה: זכור אותי

כותרת הקטגוריה

כאן אתם מוזמנים לפרסם הודעות עבודה או חיפוש עבודה.
אנא הקפידו לצרף פרטי קשר שאינם גלויים (אחרת לא נוכל להגן על פרטיותיכם)

נושאים בקטגוריה: עבודה - Jobs

2 תגובות emo
הנושא פורסם ב 14 אוק 2015 20:37 ע"י halperinko
816 צפיות
0 תגובות emo
הנושא פורסם ב 14 אוק 2015 20:49 ע"י halperinko
1085 צפיות
0 תגובות emo 1061 צפיות
0 תגובות emo 1128 צפיות
0 תגובות emo
הנושא פורסם ב 08 מרס 2014 20:30 ע"י halperinko
1796 צפיות
 
0 תגובות emo 173 צפיות
0 תגובות emo 123 צפיות
0 תגובות emo
הנושא פורסם ב 24 ספט 2017 09:35 ע"י אריק
258 צפיות
0 תגובות emo
הנושא פורסם ב 11 מאי 2017 09:05 ע"י shiri malki
429 צפיות
0 תגובות emo 590 צפיות

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

  • Measuring Quality

    Measuring Quality The concept of measuring quality can be a hot-button topic for many software testers.  This is because metrics can be used poorly; we've all heard stories about testers who were evaluated based on how many bugs they found or how many automated tests they wrote.  These measures have absolutely no bearing on software quality. A person who finds a bug in three different browsers can either write up the bug once or write up a bug for each browser; having three JIRA tickets instead of one makes no difference in what the bug is!  Similarly, writing one hundred automated tests where only thirty are needed for adequate test coverage doesn't ensure quality and may actually slow down development time.But measuring quality is important, and here's why: software testers are to software what the immune system is to the human body.  When a person's immune system is working well, they don't think about it at all.  They get exposed to all kinds of viruses and bacteria on a daily basis, and their immune system quietly neutralizes the threats.  It's only when a threat gets past the immune system that a person's health breaks down, and then they pay attention to the system.  Software testers have the same problem: when they are doing their job really well, there is no visible impact in the software.  Key decision-makers in the company may see the software and praise the developers that created it without thinking about all the testing that helped ensure that the[…]

    7.12.2019 | 8:44 קרא עוד...
  • Comparing equivalent Python statements

    While teaching one of my Python classes yesterday I noticed a conditional expression which can be written in several ways. All of these are equivalent in their behavior: if os.path.isdir(path) is False: pass if os.path.isdir(path) is not True: pass if os.path.isdir(path) == False: pass if os.path.isdir(path) != True: pass if not os.path.isdir(path): pass My preferred style of writing is the last one (not os.path.isdir()) because it looks the most pythonic of all. However the 5 expressions are slightly different behind the scenes so they must also have different speed of execution (click operator for link to documentation): is - identity operator, e.g. both arguments are the same object as determined by the id() function. In CPython that means both arguments point to the same address in memory is not - yields the inverse truth value of is, e.g. both arguments are not the same object (address) in memory == - equality operator, e.g. both arguments have the same value != - non-equality operator, e.g. both arguments have different values not - boolean operator In my initial tweet I mentioned that I think is False should be the fastest. Kiwi TCMS team member Zahari countered with not to be the fastest but didn't provide any reasoning! My initial reasoning was as follows: is is essentially comparing addresses in memory so it should be as fast as it gets == and != should be roughly the same but they do need to "read" values from memory which would take additional time before[…]

    6.12.2019 | 2:19 קרא עוד...
  • Definition of the day: Error Guessing

      Hey everyone, Here is the definition of the day: Error Guessing A test technique in which tests are derived on the basis of the tester's knowledge of past failures, or general knowledge of failure modes. Examples When you find multiple bugs during a testing phase, once all the bugs have been fixed then you ... [Read more...] The post Definition of the day: Error Guessing appeared first on The Life Of One Man.

    6.12.2019 | 4:07 קרא עוד...

טיפים

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