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

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

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

he icon   en icon

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

עדכוני בלוג אחרונים

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

הודעות אחרונות מהפורום

  • אין הודעות לתצוגה.

RSS קהילה מהעולם

בדיקות תוכנה בישראל

  • Being Taught to Report

    Being Taught to Report This evening I attended Ask Me Anything - Test Reporting with Elizabeth Zagroba hosted by Ministry of Testing. As expected it was rammed with nuggets of wisdom. Here's a handful:Test reports are not[…]

    26.01.2021 | 3:19
  • An End to End Guide to API Testing

    An End to End Guide to API Testing Click here to check out my blog post, published via Abstracta. I’ve gathered most of my API testing knowledge in one spot – to giveContinue reading

    26.01.2021 | 2:03
  • SpecSync v3.2 released / display iteration and step results in ADO!

    Learn how the SpecSync product is tested. The post SpecSync v3.2 released / display iteration and step results in ADO! appeared first on Gáspár Nagy on software.

    26.01.2021 | 10:07
  • Back to Basics – Test Bed

    Back to Basics – Test Bed In this post, let's go back to basics.😇 What is Test Bed? It's the Test Execution environment configured for Testing. Before we (Software Testers) start the Test Execution, it is highly important to[…]

    26.01.2021 | 7:26

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

  • Being Taught to Report

    Being Taught to Report This evening I attended Ask Me Anything - Test Reporting with Elizabeth Zagroba hosted by Ministry of Testing. As expected it was rammed with nuggets of wisdom. Here's a handful:Test reports are not necessarily the end. Give enough detail that your work can be understood and perhaps questioned and then the conversation can start.Test reports are not just for others. You can use them to clarify your thinking, understand your coverage, step back and choose where to go next.The reaction to your test reports is important. If no-one's listening, perhaps you need to change something. Better still, ask what your stakeholders want to hear from you as well or instead.If you're not sure whether something makes sense to report, ask someone you trust before reporting it.One style of report does not fit all uses. Format, content, length, style, and so on can all vary depending on the context. You can report during testing as well as afterwards. Externalise your thoughts for yourself or those you're working with.Elizabeth also mentioned the Rapid Software Testing story format for reports. I take a version of that as a good basic default, and I cast it like this:What I did What I foundRisks and valueValue might be stuff that stakeholders particularly wanted to know has been covered, risks will include new uncertainties uncovered in this work. Things I didn't do, but which could be relevant, will go into the risks section. 

    26.01.2021 | 3:19 קרא עוד...
  • An End to End Guide to API Testing

    An End to End Guide to API Testing Click here to check out my blog post, published via Abstracta. I’ve gathered most of my API testing knowledge in one spot – to giveContinue reading

    26.01.2021 | 2:03 קרא עוד...
  • SpecSync v3.2 released / display iteration and step results in ADO!

    Learn how the SpecSync product is tested. The post SpecSync v3.2 released / display iteration and step results in ADO! appeared first on Gáspár Nagy on software.

    26.01.2021 | 10:07 קרא עוד...

טיפים

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