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

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

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

he icon   en icon

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

הקהילה

אבינעם תמונות - PC140010

  • 3
בתמונה זו:

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

  • Intro to Pace Layered Application Strategy

    Intro to Pace Layered Application Strategy Just like products across different industries are not the same, similarly software products are not the same either. While I used to understand that difference, but perhaps did not appreciate how different they can be and how they should be classified and treated differently. Recently I came across Gartner’s PACE layered application strategy giving a new perspective which can be very helpful for managing multiple products or programs. Premise of the strategy It was realised that certain applications don’t change a lot and need to be more cost effective and stable than efficient, while others had to be delivered very quickly and change frequently. Both require different processes and should focus on different goals. A mobile app compared to a mainframe application are not the same. Clearly both serve very different markets and have unique requirements, hence no single strategy can be used for both. In 2010 Gartner introduced a concept where different applications in an organization can be delivered at a different ‘pace’, meaning some would have shorter release cycles and are more flexible, while other applications would be slower and more robust in delivery. Understanding which applications need rapid delivery and change and where this is not a requirement is important. Also applications under these categories should not be organized around each other since the required results are different. Pace Layers From rapid deployment and flexibility to slow releases and stabile products, there are three layers defined with unique characteristics providing the needed support to one another. Systems[…]

    19.01.2019 | 8:21 קרא עוד...
  • Reverting Ruby Hash So That Array Values Become Keys, And Keys become Values

    TL;DR Dale Emery @dhemery ask this question on Twitter. I responded with Gist solution. The Problem Is there a canonical/idiomatic way in Ruby 2+ to invert a hash whose values are arrays, so that the resulting hash uses the values in… Continue Reading →

    19.01.2019 | 7:34 קרא עוד...
  • Easy Free Automation Part I: Unit Tests

    Easy Free Automation Part I: Unit Tests This post is the beginning of an eight-part series on easy, free ways to automate each area of the Automation Test Wheel.  It's been my experience that there are a number of barriers to learning test automation.  First, the team you are on might not need certain types of automation.  For example, my team has been solely API-focused, so for the last two years I haven't had much reason to do UI automation.  Second, your company may already have invested in specific automation tools, so when you want to learn to use a different tool, you need to do it on your own.  Third, there are many tools that have barriers to using them, such as a high cost or a complicated setup.  And finally, there is not always good documentation out there to help people get started.In this series, I'm hoping to provide simple, free examples that will demonstrate each area of the Automation Test Wheel in practice, which you can use as a jumping-off point in your own automation journey.  We'll begin with unit tests.Unit tests are usually written by developers, but it's a good idea for all software testers to understand what they are and how they work.  Unit tests test just one method or function, and they aim to exercise as many paths of that method or function as possible.  The major benefit of unit tests is that they provide extremely fast, accurate feedback.I'm going to use Python and Pytest to demonstrate how unit tests work. […]

    19.01.2019 | 7:24 קרא עוד...

טיפים

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