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

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

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

he icon   en icon

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

הקהילה

הקהילה

אין לכם הרשאות מתאימות, נא צרו קשר עם מנהל האתר

התחבר עכשיו!

הצטרפו לקהילה והכירו אנשים חדשים

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

  • Product Mapping and Quality Insight

    Product Mapping and Quality Insight Previously I talked about project management and a quality focus. Here I want to take both down a level to get a little more practical, specifically around the idea of how that quality focus strongly encourages delivery teams to create product maps. It’s those product maps that will give a team the first insights into what quality is going to look like. This notion or product mapping is where I think product management (and thus product mangers) and product development (and thus product developers) start to to intersect. Since there are many very specific ways to craft a product map in a given tool — including using no tool at all! — I’m going to remain largely agnostic of tool concerns here and instead just focus on the idea of product mapping as a technique. The product map, as an artifact, is of course also important. So what is this “product map” thing? Well, the product map is generally a high-level visual summary that maps out the vision and direction of your product over time. The goal here is to convey the strategic direction for the product and tie the product direction back to the strategy for the company as a whole. Crucially, it’s important to note that a product map is not one over-arching view of the entire product. In fact, there will likely be multiple product maps. Specifically, and I think this is a good way to frame it, you will have one product map per market promise.[…]

    1.08.2021 | 2:38 קרא עוד...
  • Creating a Quality Strategy

    Creating a Quality Strategy In my last post, I introduced the concept of the Quality Maturity Model: a series of behaviors that help teams attain various attributes of quality in their software. One of the things it’s important to note is that adopting a Quality Maturity Model requires the whole team to contribute to quality. Quality is not something to be thrown “over the wall” to testers; rather it is a goal that both developers and testers share. But how can you get the whole team to own quality? One way is through the creation of a Quality Strategy. A Quality Strategy is a document that the whole team agrees on together. It’s like a contract that describes how quality software will developed, tested, and released by the team. In this post, I’ll discuss some of the questions you may want to answer in your team’s Quality Strategy. Creating and Grooming Stories:How does the team decide what stories to work on? This could be a decision by the whole team, or by the product owner only. Or the prioritization could be done by someone outside the team. Who grooms the stories to get them ready for development? This could be the whole team or a subset of the team. Ideally, you’d want to have at least the product owner, one developer, and one tester participating. Development Process:How does the team decide who works on which story? It could be that the developers can pick any story from the board, or it could be that[…]

    1.08.2021 | 8:46 קרא עוד...
  • API Testing Challenges - How To Use Simulation Mode

    This post and video shows how to use the Simulation Mode in API Challenges. What are the API Challenges? Our API Challenges Application has a fully functional cloud hosted API, and a set of challenges to work through. Overview The API has a simulation mode, this allows you to experiment with different tools in a controlled environment. Watch on YouTube Patreon ad free version Simulation Mode The simulation mode uses hard coded data in responses, but tries to mimic some conditions. e.g. it expects you to post a specific JSON payload or XML payload and responds ‘as if’ you sent it. But… it also checks if you sent valid json, or valid xml, and responds based on your headers e.g. returning XML if you ask for it. The simulator is stateless and does not track your usage, making it deterministic for multiple users. Which means: Entities created do not show in the ‘entities’ call, but can be retrieved by a ‘GET’ Entities deleted do not show in the ‘entities’ and respond to a 404, but the delete for them will return a 200… you can only delete ‘specific’ entities, other entities will respond with a forbidden request. etc. there are ‘inconsistencies’ but they are logical based on the needs of a stateless simulator. Use the actual API that underpins the challenges if you want a ‘real’ API. Try the verbs and payloads listed below as a way of making sure your tooling is setup and you understand the absolute basics[…]

    1.08.2021 | 5:00 קרא עוד...

טיפים

  • אף פעם אל תפסיקו ללמוד - בדיקות
    אף פעם אל תפסיקו ללמוד - בדיקות אף פעם אל תפסיקו ללמוד - בדיקות " אף פעם אל תפסיקו ללמוד" – או כמו שנאמר "רק טיפשים יודעים הכל". מפעילותי בפורומים השונים בעולם הבדיקות בארץ ובעולם, תכופות אני רואה כיצד דווקא חסרי הניסיון, שרק…
    קרא עוד...
  • בודק - עקוב אחרי בודקים אחרים בטוויטר ובבלוגים
    בודק - עקוב אחרי בודקים אחרים בטוויטר ובבלוגים בודק - עקוב אחרי בודקים אחרים בטוויטר ובבלוגים, חלוק רעיונות והתנסויות, כתוב, קבל משוב ושפר את יכולות ההתדיינות – נראה כי היתרונות בעולם הטוויטר חמקו מעיני קהילת הבודקים הישראלית אשר לרוב דווקא ממהרת לאמץ ומשתלבת בסביבות…
    קרא עוד...
לרשימה המלאה >>