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

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

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

he icon   en icon

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

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

פרופיל משתמש Michael Stahl

Michael Stahl's Avatar
  • מנותקים
  • דירוג: Junior Boarder
  • תאריך הרשמה: 02 יונ 2013
  • זמן: GMT +0:00
  • זמן מקומי: 20:53
  • פוסטים: 24
  • תודות שהתקבלו 3
  • צפיות בפרופיל: 448
  • קארמה: 1
  • מיקום: Unknown
  • מגדר: לא ידוע
  • תאריך לידה: Unknown



פוסטים אחרונים

אין פוסטים

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

  • Preparing yourself for the CTFL Exam

    Preparing yourself for the CTFL Exam A friend of mine has recently passed the CTFL Exam after one week of a lot of study and effort. CTFL is a popular Certified Tester Foundation Level exam in software testing. It examines your professional knowledge around software testing discipline. The exam has 40 questions and takes 60 minutes. Should I take the exam ? This is a very debatable subject and people can discuss for hours about it’s value. If you are thinking about if this is for you or not, these are some things that you can keep in mind and help you to decide: Experience always has more value than any certification. Certifications don’t provide the exposure and training you get while working on real life projects !THIS CERTIFICATION CAN HELP YOU TO GET YOUR FIRST QA JOB. If you are changing careers, never worked with Software Testing before, then this certification might help you to be selected for an interview. This would be part of your portfolio and as you might not have any experience in this field, this can be used as a parameter when filtering the candidates.THE CERTIFICATION DOESN’T MEAN YOU ARE AN EXPERT OR THAT YOU ARE GETTING THE JOB. Most of the professionals applied to this certification in the beginning of their career and then never study the Syllabus again. This is because you start to use your experience more than the base knowledge you got when studying for the exam. Again the certification doesn’t mean you will get the job,[…]

    26.10.2020 | 1:00 קרא עוד...
  • Testing on the Toilet: Testing UI Logic? Follow the User!

    Testing on the Toilet: Testing UI Logic? Follow the User! This article was adapted from a Google Testing on the Toilet (TotT) episode. You can download a printer-friendly version of this TotT episode and post it in your office.By Carlos Israel Ortiz GarcíaAfter years of anticipation, you're finally able to purchase Google's hottest new product, gShoe*. But after clicking the "Buy" button, nothing happened! Inspecting the HTML, you notice the problem:<button disabled=”true” click=”$handleBuyClick(data)”>Buy</button>Users couldn’t buy their gShoes because the “Buy” button was disabled. The problem was due to the unit test for handleBuyClick, which passed even though the user interface had a bug: it('submits purchase request', () => { controller = new PurchasePage(); // Call the method that handles the "Buy" button click controller.handleBuyClick(data); expect(service).toHaveBeenCalledWith(expectedData);}); In the above example, the test failed to detect the bug because it bypassed the UI element and instead directly invoked the "Buy" button click handler. To be effective, tests for UI logic should interact with the components on the page as a browser would, which allows testing the behavior that the end user experiences. Writing tests against UI components rather than calling handlers directly faithfully simulates user interactions (e.g., add items to a shopping cart, click a purchase button, or verify an element is visible on the page), making the tests more comprehensive.The test for the “Buy” button should instead exercise the entire UI component by interacting with the HTML element, which would have caught the disabled button issue: it('submits purchase request', () => { // Renders the page with the “Buy” button and its associated code. render(PurchasePage); //[…]

    26.10.2020 | 12:05 קרא עוד...
  • Testing AI products

    How would you go about testing an AI product? Join me at QA&TEST Conferences where we will debate the topic on Oct 30. I’ve been fortunate to work on that problem a few times in past years, in my experience this is not a straight forward answer.. Biggest reason for me – it’s not easy to establish clear oracles (I didn’t use the word requirements..) which creates a complete new dynamics to test these products. The test objectives of these systems are therefore going to be a bit different, and wouldn’t be just about testing the actual model, I’d stretch it from the beginning – ‘capturing of data’ and then take to the other extreme – ‘is the model predictions good enough’ – not an easy answer to give, but worth investigating. The post Testing AI products appeared first on Quality Spectrum.

    26.10.2020 | 11:31 קרא עוד...


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