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

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

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

he icon   en icon

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


סרטונים של chen

chen לא הוסיפ/ה תמונות עדיין

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

  • Orchestrating System Test Automation for Visual Thinkers

    Orchestrating System Test Automation for Visual Thinkers Working on a sizable system, feature after feature I found us struggling with timeliness of completing testing. Each feature kickoff, testerkind showed up to listen, and start learning. While development was ongoing, more learning through exploring took place. And in the end, after feature was completed, tests were documented in test automation, and just in case time taken for some more final exploring. It seemed like a solid recipe, but what I aspired for is finding a way where testing could walk more in sync with the development. The learning time was either half-attention, or elsewhere occupied, and it resembled a mini-waterfall for each feature. I formulated an experiment, with the intent of learning if being active with test automation implementation from the start would enable us to finish together. And so far, it is looking much better than  before.The way I approached test automation implementation was something I had not done before. It felt like a thing to try, to move focus from testerkind listening and learning to actively contributing and designing. In preparation for the feature kickoff, I draw an image of points of control and visibility, tailored to the specific feature.As I don't want to go revealing any specific of what we build, I drew a general purpose illustration of the idea. Each box on the main line were touch points where development for the feature would happen (pinks). Each box on the side was a touch point already existing in the system, found by analyzing the system for[…]

    24.11.2020 | 2:24 קרא עוד...
  • Three notes on Value Streams

    These are some scattered notes from a DevOps Toronto meetup earlier this year. These are highlights from a presentation by Steve Pereira on value stream mapping. I’ve been finding making value streams explicit, whether formal or not, a key part of my role evolving from testing to DevOps more generally. One of the basic strategic things that I think testers can do is make explicit what each step of the process to getting an idea out to production actually is, why it is there, what differentiates it from other steps, and what value it adds to the process. 1. On structuring value streams At a granular level, when laying out a stream from Step 1 to Step 2 to Step 3, take note of how long each step takes and how long of a gap is between steps. Both a long step and a long wait time are opportunities for streamlining. When one step fails, what step do you have to go back to, and what’s the likelihood of that happening? It might be that you’re repeating a costly step more often than you need to be. At a higher level, value streams should be like Google Maps; You should be able to look at continents, but also to zoom down into countries, cities, and neighbourhoods. In my work right now I’m focusing on the steps to get a commit into production through the CI/CD pipeline, but that’s only one piece of a broader picture. The product owner might zoom[…]

    24.11.2020 | 9:00 קרא עוד...
  • Testing Machines that Think

    The Risks, Challenges and Opportunities for Testers Giving a signal boost for my new colleagues at KPMG UK for their first of a series of testing webinars. In this webinar, to be held virtually on Wednesday 2 December between 16:00–17:00 GMT, we will discuss Artificial Intelligence (AI), Machine Learning (ML) and other related technologies through […] The post Testing Machines that Think first appeared on Quality Remarks.

    24.11.2020 | 8:30 קרא עוד...


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