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

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

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

he icon   en icon

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

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

כותרת הקטגוריה

ברוכים הבאים לעולם הבדיקות, כאן אתם מוזמנים לשאול כאוות נפשכם לגבי מקצוע הבדיקות וה-QA, כיצד ניתן להיכנס, מה כדאי ללמוד, היכן כדאי ללמוד, שאלות מראיונות וכד'.
(אנא הקפידו על טוהר הפורום - טענות כלפי גורמים שונים יש להעלות תוך גיבוי עובדתי ובצורה מכובדת, פרסום סמוי ללא גילוי נאות אסור בתחליט האיסור - כתיבת עובדות והמלצות מותר)
כאן אין לפרסם הודעות עבודה או חיפוש עבודה - אלא רק בפורום המתאים.

נושאים בקטגוריה: חדשים, הדרכה - Newbies

19 תגובות emo
הנושא פורסם ב 13 יונ 2013 21:49 ע"י halperinko
13k צפיות
1 תגובות emo 1767 צפיות
1 תגובות emo 1529 צפיות
0 תגובות emo 1585 צפיות
0 תגובות emo 577 צפיות
0 תגובות emo
הנושא פורסם ב 01 יונ 2017 05:12 ע"י halperinko
516 צפיות
0 תגובות emo
הנושא פורסם ב 19 ינו 2017 17:39 ע"י halperinko
693 צפיות
1 תגובות emo
הנושא פורסם ב 05 ינו 2017 20:58 ע"י halperinko
2216 צפיות
1 תגובות emo 1109 צפיות
0 תגובות emo
הנושא פורסם ב 31 אוק 2016 07:47 ע"י halperinko
525 צפיות

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

  • Five for Friday – January 24, 2019

    This is the special time travel edition of FfF (I lost a day – mentally – while traveling). I have read, and re-read this article on Work is Work. It’s a fantastic analysis of organizational design. I plan on reading it yet again after I post this.It’s no secret that I like Radical Candor, and in order to care personally, you need to get to know your team. Mike Cohn posted 25 Questions that Will Help You Know Your Teammates Better this weekSpeaking of feedback, Negative Feedback Rarely Leads to ImprovementTwo github links to close things out – the first is The Book of Secret KnowledgeThe second github link is a curated list of Chaos Engineering topics. This one is staying in my favorites. (potentially) related posts: Five for Friday – January 19, 2018 Five for Friday – October 4, 2019 Five for Friday – January 4, 2019

    25.01.2020 | 3:22 קרא עוד...
  • How to Stamp Out Intermittent Testing Issues With Periodic Automation

    How to Stamp Out Intermittent Testing Issues With Periodic Automation Originally published by TechBeacon.com. In the pop culture of the United States, Sasquatch (a.k.a. Bigfoot) is a legendary and elusive ape-like creature infrequently seen in the Pacific Northwest. In the software realm, we have our own version of Sasquatch: those irritating, sometimes catastrophic, issues that are hard to reproduce. So, as a test engineer, how do you track down your own elusive Sasquatch? I use an approach I call “periodic automation,” and it works quite well. Traditionally, you run your automated tests on event boundaries such as when you’ve had a successful deployment. Why? When a deployment succeeds, it was initiated because some code changed in your application. To be effective with your time, you look for problems when you think they may have been introduced. Logically, points of change are where you expect to see issues injected, so you tend to only look for issues then. Unfortunately, this approach limits your opportunities to reproduce the previously mentioned intermittent issues: hard-to-reproduce issues that don’t occur on a predictable schedule or set of events. If, however, you also run your automation periodically, in addition to your event boundaries, you’ll have additional opportunities to reproduce these types of issues. Here’s how periodic automation works. Highly connected software is prone to intermittent issues Today’s software is highly connected, both to components in your production network and to servers and components outside of it. Analytics, payment, and social media services, for example, are often external to your application’s network. Reliance on these services makes your environment harder to test. Just enumerating all[…]

    25.01.2020 | 1:00 קרא עוד...
  • Would Heu-risk it? Part 12: The Twins

    Would Heu-risk it? Part 12: The Twins Another weapon for you to weild! I have some funny stories of how wrong things can end up when this fails. First as usual, rhyme-time: “Your process might work like a charm with one clientMake sure you´re not on a single queue reliantWhat happens the day more than one person tryAnd simultaneously demand the same thing to buy” So, what does it mean? Have you ever been to a web shop, browsing through. You see something you are interested in buying and you put it in your cart. After some more shopping you try to check out – only to be told that the item is no longer available! Can you remember how annoying that was? Well, this card is about that, sort of.See, threading is something that can mess up a lot of things. In the example above, it might be a concious decision from the store to not reserve your item – more of a first come – first serve approach. Which can be ok, of course, but if it gets too common it might cost you users. So, imagine each task someone tries to do in your system as one of the clients above. They each have something they want to buy, and they all think their request is the most important one. Your application’s job is to make sure you don’t mess up their orders, while still serve everyone as quickly as possible.Imagine threading as queues in the department store. Every cashier is a separate thread[…]

    24.01.2020 | 7:00 קרא עוד...


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