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

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

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

he icon   en icon

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

הקהילה

Boris Sionov חברים

אין חברים כרגע

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

  • What is continuous testing?

    By Lisa Crispin Even when I worked on waterfall teams, we tested early and often. We got ourselves invited to analysis and requirements meetings. We tested requirements docs. We asked questions. We tested as the developers delivered code, even before “code freeze”. We also worked closely with customer support to learn about how customers used the features after they were delivered. (I realize not all teams using a phased-and-gated approach do all that, but that approach should not stop teams from using good practices!) Extreme Programming (XP) made so much sense to me because it embraced testing and quality as the responsibility of the entire delivery team. In agile development, we focus on building quality in, we test ideas, we automate regression tests, we explore delivered code, we test in production. These same practices apply to teams who use the “DevOps” label as well. That’s why Dan Ashby’s post in 2019 on “continuous testing” resonated so much with me. His visual model captures what is in my brain when I see the term “continuous testing”. With his permission, I often use this model to help others understand the concept: But there are different definitions! Recently, someone posted a link to a short Twitter thread from earlier this year where continuous testing was defined quite differently. Basically, this alternative definition is only about running automated tests in the continuous integration, delivery, deployment pipelines. I started asking around to see how other people define “continuous testing”, and some people shared that definition[…]

    19.07.2019 | 4:33 קרא עוד...
  • Concentrate.

    So I’m a bit of a higgledy piggledy person in general, a messy storm of ideas. Don’t get me wrong, I can be Rand Al Thor with his flame in the void, focussing on one task or feeling until it’s done. But just like Rand Al Thor, I have a tendency to take on too much, juggling tasks until I become a miserable old sod no one wants to be around because I have so much to do, don’t you understand how stressful it is just to be me? (Rand is a fictional character in the fantasy series The Wheel of Time by Robert Jordan) To help me reign in and control some of the tendencies for picking up more and more tasks until I get overwhelmed by my own stupidity and shortsightedness, I have been using a Trello board to track everything I want to do. I wrote a blog post about it at the time I began, and I suppose this is the update on how that’s going and how my process has evolved since then. The Toggl Incident An aside on efficiency and my learning habits: there was an incident, I call it The Toggl Incident. For about a month, I used toggl.io to track how much time I spent on various tasks by separating them into different types. See below for an example from one week: Manual Testing 43% – Meetings 37% – Personal Development 11% – Devving 7% – Regression 1% (note that on the[…]

    19.07.2019 | 3:03 קרא עוד...

טיפים

  • אל תחכה שיתנו לך הזדמנות
    אל תחכה שיתנו לך הזדמנות אם אתה רוצה להתפתח - אל תחכה שיתנו לך הזדמנות, קח אותה - למד, בצע והדגם הדבר בזמנך הפנוי - מישהו כבר יאמץ את זה וייתן לך את הקרדיט.   טיפים מחברי ITCB-AB
    קרא עוד...
  • בודקים - זכרו כי מדובר באנשים
    בודקים - זכרו כי מדובר באנשים בודקים - זכרו כי מדובר באנשים "זכרו כי מדובר באנשים" (Tony Bruce) – בסופו של יום – כל מוצר ותוכנה מיועד לשרת צרכי אנשים. לעיתים מדובר בקהל אבסטרקטי שאיננו מכירים באופן אישי ואין לנו גישה אליו,…
    קרא עוד...
לרשימה המלאה >>