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

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

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

he icon   en icon

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

הקהילה

cover photo

Yaron Adler

שלח מסר
הוסף כחבר
Yaron Adler

אודותי

מידע בסיסי

חבר מתאריך
רביעי, 08 ינואר 2014 08:15
האחרון שהיה און ליין
5 שנים
  • Yaron Adler הגיב לנושא 'Skybox Security - Experienced QA Engineer position' בפורום.
    7 שנים

    גייסנו אחד אבל עדיין מחפשים אחד נוסף.
    אם את/ה בודק תוכנה מנוסה, מקצוען אמיתי עם רקע ברשתות/פייוולים/סייבר סקיוריטי, נשמח לקבל את קורות החיים שלך.
    קרא עוד...

  • Yaron Adler יצר נושא חדש ' Skybox Security - Junior QA Automation Developer - student position' בפורום.
    7 שנים

    [File Attachment: logo_2014-07-01.gif]
    Skybox Security is looking for a talented developer to join the Skybox QA Testing Automation Team as a part-time employee at its Herzlia-Pituach R&D center. Skybox QA Testing Automation Team developers create and maintain tests of a highly complex product that has both Java and Web-based user interfaces

    Requirements
    B.Sc. (or Student) in Computer Science or an equivalent engineering field
    Proficiency in at least one programming language: Java, VBScript or similar
    Expected service span of at least two years
    Persistence, patience and thoroughness

    Advantages
    One-three years of experience in UFT (QTP) or Selenium automation testing tools
    Previous experience in Scripting using Python/Perl/bash
    Knowledge and experience in formal software testing procedures

    Please refer relevant CVs to: This e-mail address is being protected from spambots. You need JavaScript enabled to view it.

    קרא עוד...

  • Yaron Adler יצר נושא חדש ' Skybox Security - Experienced QA Engineer position' בפורום.
    7 שנים

    [צירוף קובץ: logo.gif]
    Skybox Security is looking for an experienced QA engineer for a challenging position at its Herzlia-Pituach R&D center. Members of the Skybox QA Team test a highly complex software product requiring in-depth understanding of Networking and Cyber Security.

    Requirements
    Three+ years of experience in manual software testing of enterprise-grade software products
    Knowledge and experience in formal software testing procedures
    Knowledge and understanding of Cyber security, related risks and mitigation technologies
    B.Sc. in computer science or an equivalent engineering field
    Persistence, independence and thoroughness

    Advantages
    Previous experience as a QA engineer in a software company developing Networking or Security products, such as Firewalls, IDS/IPS, Vulnerability scanners
    Previous experience in areas such as Penetration testing, Cyber Security, Ethical Hacker certification

    Please refer relevant CVs to: This e-mail address is being protected from spambots. You need JavaScript enabled to view it.

    קרא עוד...

חברים

אין חברים כרגע

קבוצות

לא הצטרפת לקבוצות עדיין.

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

  • Creating Jest Unit Tests for AWS Step Functions

    Creating Jest Unit Tests for AWS Step Functions You’ve used AWS Step Functions in your code and now you want to create some nit tests for it? I’ve got just the article for you.Continue reading on Medium »

    22.06.2021 | 6:34 קרא עוד...
  • RIMGEA (2nd ed.) aka RIMGEN

    Wow, it’s been 10 years since this blog post: RIMGEA – 6 approaches to bug reporting. There I wrote about a very useful mnemonic I picked up from a bug advocacy class (it’s more about bug reporting, than loving bugs). Lately, I’m not in a role where functional testing is part of the official R&R. But I think I’m a tester through and through — I still test or review, and I still log bugs or give feedback. And I still care about how bad bug reporting can give testing a bad rap. So anyways, now’s a good time as any to retouch that post. RIMGEN (and maybe plus S) Originally, the mnemonic I picked up from the bug advocacy class was “RIMGEA“. It stood for the 6 factors or approaches to bug reporting which are: Replicate, Isolate, Maximize, Generalize, Externalize, And say it dispassionately. Then there was a suggestion in the comments before and I also found some recent BBST material that made the shift from “A” to “N” to suggest the neutrality in tone. The last letter S was from the comments, with a suggestion to spellcheck. I would generalize it as proofread but RIMGENP doesn’t roll off the tongue quite easily. Replicate it – Try to replicate the bug. If you can’t replicate it yourself, then it might be harder to persuade your developer to fix a problem that they can’t see. This also doesn’t only benefit the developer. Somewhere down the line, you or a fellow[…]

    22.06.2021 | 1:07 קרא עוד...
  • Five Blogs – 22 June 2021

    The (best) five blogs we can read today. Check them out. 3 Mindsets High-Performing Business Leaders Use to Create Growth Written by: Raj Subrameyer I Think in Flowcharts Written by: Michael Lopp How Much Testing is Enough Written by: George Pirocanac Testing, Quality, and my inability to teach Written by: Patrick Prill Automation Testing on Microservices Written by: Bishma Nishadi Quote of the day: “Change requires intent and effort. It really is that simple.” -Roxane Gay You can follow this page on Twitter

    21.06.2021 | 11:08 קרא עוד...

טיפים

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