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

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

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

he icon   en icon

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


cover photo


שלח מסר
הוסף כחבר


מידע בסיסי

  • גיל

  • אודותיי

חבר מתאריך
חמישי, 06 מאי 2021 18:10
האחרון שהיה און ליין
אף פעם לא התחבר


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


לא הצטרפת לקבוצות עדיין.

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

  • CODS It!

    CODS It!  Over on the Association for Software Testing Slack our book club facilitator, Zenzi Ali, is guiding us through Elisabeth Hendrickson's Explore It! Last week she posed this question:"When joining a new team/job/project, how do you determine the core capabilities of the software you’ll be testing?"I surprised myself a little with my answer. Not because of what I described, but because I hadn't mapped it out this way before. It was only when I stepped back to try to summarise that I noticed the pattern in my intuitive behaviour. So here's what I wrote, edited so that it's less of a stream of consciousness.--00-- Rob Meaney has a great talk, A Tale of Testability, where he describes how his CODS criteria (controlability, observability, decomposability, simplicity) were applied to a product he worked on to make it more testable.  Now, I'm not suggesting that someone walks into a new team and shouts about re-engineering for testability before they've even taken their coat off! I am suggesting that the same four perspectives can be valuable ways to explore a product to learn what it's about. In the last 18 months I've joined teams, joined projects, and inherited products and each time I've found value in this approach. Control. I like to try to get a copy of the system under test running locally, under my control. This can be tricky and perhaps initially it'll only be possible in the environment the developers are using to build the software, including IDE etc.  That's OK. I[…]

    27.11.2022 | 12:57 קרא עוד...
  • How to Lint K6 Tests and add a pre-commit hook

    You'd think linting your K6 tests would be straight forward, but because K6 is written in GoLang it complicates it. In this post I show you how to lint K6 tests and add a pre-commit hook with Husky. The post How to Lint K6 Tests and add a pre-commit hook first appeared on Stuart Thomas.

    26.11.2022 | 10:01 קרא עוד...
  • Performance testing APIs in pipelines? K6 makes it simple!

    Performance testing often gets neglected. With K6 it is quick and easy to build simple load tests to add to your pipeline! The post Performance testing APIs in pipelines? K6 makes it simple! first appeared on Stuart Thomas.

    26.11.2022 | 8:48 קרא עוד...


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