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

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

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

he icon   en icon

TenKod EZ TestApp - Mobile Apps Testing

נכתב על ידי 
ראשון, 24 אוגוסט 2014 04:49
דרגו כתבה זו
(1 הצבעה)

I'm extremely excited to announce the public availability of TenKod's EZ TestApp 3.0 – the revolutionary Mobile Application Testing solution is out today.

Our ongoing dedication to innovation, together with the hands on experience and challenges we have gained over the years in the test automation arena, has enabled us to deliver the best of breed testing solution which optimizes user experience, while exceeding industry standards. EZ TestApp 3.0 is a product of how we've been imagining mobile test automation solutions should be.

EZ TestApp has proven to be a huge success in reducing the mobile development and testing efforts and delivery cycle times for our customers. The feedback from our users' community – developers and testers. All emphasized this is the best product they have used incorporating all their requirements to shorten the development cycle process to release a high quality product

EZ TestAppEZ TestApp fits seamlessly within our customers' existing development and testing landscapes, and makes tedious automation tasks a breeze. The ultimate goal of EZ TestApp is to create a flawless and simple mobile testing experience from start to finish, independent from the mobile platform.

You are warmly invited to download our free trial version, enjoy the new innovative solution for mobile application testing development solution.

TenKod was founded by a group of developers and quality professionals with a passion for software testing. Our combined decades of experience in innovating and implementing test software platforms, test frameworks and continuous integration solutions across different organization sizes, have paved the way for this day in which we release to the world the best mobile test automation solution, EZ TestApp.

We believe that success derives from our focus on innovation and execution. Innovation to us means doing things better and smarter. It means making the most out of our resources, empowering people to do what they do best and utilizing the power of diverse ideas to overcome challenges, and last but not least to be attentive to our community, use your important feedback. All of the above provide the best of breed solution we released today – TenKod EZ TestApp.

We are here to make the life of Mobile Apps developers and testers better!

Mobile Apps developers seek to do more with less, you will find a partner in TenKod. Our products will help you manage your development and test efforts of mobile applications across the enterprise and in the public, private and hybrid clouds.

We intend to keep on innovating and executing, and update you along the road about our progress.

Talk to you soon and I invite you to join our community.

Asaf Saar,
TenKod CEO

http://www.tenkod.com 

 

TenKod Mobile Application Testing EZ TestApp

שונה לאחרונה ב שבת, 29 נובמבר 2014 05:32

מדיה

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

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

  • Using Retries in tests can hide the bugs

    Using Retries in tests can hide the bugs We are quite familiar with the concept of randomly failing automated tests. Those are the tests that even though there is no change in the feature they are testing, they either fail randomly at the same step, or they fail at random steps. Handling the results of such tests can be tricky, and some teams choose to simply retry a test if it failed. But is that the best option? Here are my thoughts. First of all, we need to ask ourselves why these tests are failing randomly. Here are a few possible reasons: the test environment is unreliable. Too often a test environment does not have enough hardware resources to work properly under the load our automation generates. Or, it could be configured incorrectly. we are not using waits (if we are talking about Selenium tests). The test itself is not properly written to account for asynchronous events that take place in the UI we are testing. In some cases the use of Javascript is making it harder on our tests to be reliable. In order to have a green test results report after the tests ran, a retry mechanism is often put in place. It can re-run the failing tests either only once, or a chosen number of times. However this can hide the fact that the tests did really fail for a reason, and the reason was that there is a bug in the system. Because the test failed at the first run, but could pass at[…]

    14.04.2021 | 1:20 קרא עוד...
  • Five Blogs – 14 April 2021

    The (best) five blogs we can read today. Check them out. Catch 22 and The Kobayashi Maru Written by: Steve Keating Pipelines as code… not text Written by: Beastmode Achieve More with Less: Pareto’s Principle in Software Testing Written by: Prashant Hedge The thrill of testing Written by: Paul Seaman Is Critical Thinking Dead? Written by: Randy Gage Quote of the day: “The present changes the past. Looking back you do not find what you left behind.” -Kiran Desai You can follow this page on Twitter

    13.04.2021 | 11:22 קרא עוד...
  • What I learned from Practitest’s State of Testing Report 2021

    What I learned from Practitest’s State of Testing Report 2021 Look at the rules, not the exceptions Now in its 8th year, the SOT Report provides testers with some valuable trend-based information on all things testing. The full report in all of its chart based glory was delivered today, and is well worth bookmarking. You can read the full report here. Sometimes, when attending meetups, conferences or reading online articles, the loudest voices are often those with the most exceptional experiences. But we may discover this fact long after our own Imposter Syndrome has reprimanded us for not living up to their ideals. We may find ourselves wondering “I’ll never be a proper tester, I don’t even write unit tests” or “I’ve never done test coaching/worked on IoT technology/done BDD/shifted left/[insert plethora of missing skills]” so is there even a future for me in this industry? Stats tend to be more accurate at revealing general trends. As I did at my Testbash Manchester talk, rather than focusing on the exceptions, I want to pull out some of the rules. How the majority of people who consider themselves to work in Testing define what they do, what they call themselves, and how they work. Nope, its not sexy. But it is reassuring to learn that out of all the responses:- 28% are known as “Test/QA engineers”, only 0.89% Test Coach and 2.14% are SDETS.74% and 60% test Web and Mobile, only 9% IoT and 18% Big Data.92% work in Agile environments, only 27% use BDD.75% have tasks that involve Test Automation[…]

    13.04.2021 | 2:14 קרא עוד...

טיפים

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