Download as PDF, PPTX
Uploaded byGlobalLogic Ukraine
GlobalLogic QA Webinar “What does it take to become a Test Engineer”
The document covers the journey and skills needed to become a test engineer, highlighting the importance of software testing and its historical development. It outlines essential soft and hard skills, dispels myths about testing as a profession, and provides tips for crafting a successful resume for freshers. Additionally, it includes recommended resources and references for further learning in software testing.
More Related Content
Similar to GlobalLogic QA Webinar “What does it take to become a Test Engineer”
GlobalLogic QA Webinar “What does it take to become a Test Engineer”
- 1.
- 2. 2 What Does ItTake To Become A Test Engineer Olena Lendiel Middle QA Engineer 17.08.2022
- 3. 3 Agenda 1. Why softwaretesting? 2. The history of software testing 3. Good to have skills 4. Finding your niche 5. Software testing myths 6. Successful resume for freshers 7. Recommended resources
- 4.
- 5. 5 Let’s get acquainted! OlenaLendiel ● Middle QA Engineer ● ISTQB FL Certified Tester ● Mentor, trainer and coordinator at GlobalLogic Manual QA Bootcamps ● Relocated to GlobalLogic Germany ● A switcher :) Me then: Early music educator Me now: Test Engineer
- 6. 6 Why do youwant to do a testing job? You should have a clear answer to the questions below: ● Why do you want to become a Software Tester? ● If you are a computer science engineer, why did you not choose Software Development? ● If you are from some other stream, why don’t you look for a job in your field of specialization?
- 7. 7 7 The History ofSoftware Testing
- 8.
- 9. 9 The History ofSoftware Testing 1979 - 1982 Destruction Testing activities were focused on finding errors 1983 - 1987 Evaluation During software life cycle, product is evaluated and quality is measured … - 1956 Debugging No clear difference between testing and debugging 1957-1978 Demonstration The goal was to show that software satisfies the requirements 1988 - … Prevention Current approach is to prevent faults in requirements, design and implementation link to the source
- 10. 10 The History ofSoftware Testing Debugging link to the source
- 11. 11 Debugging - OrientedPeriod 1843 Ada Lovelace - The first programmer 1837 The first computer (Analytical Engine) 1878 Thomas Edison: The first using the term ‘Bug’ 1947 The first documented computer bug 1951 Three processes for the quality management: quality planning quality control quality improvement 1954 The first high-level programming language
- 12. 12 The History ofSoftware Testing Debugging Demonstration
- 13. 13 Demonstration - OrientedPeriod 1958 First software test team (Project Mercury) 1969 Edsger Dijkstra ‘Testing shows the presence, not the absence of bugs’ 1969 Decision tables were introduced by Burton Grad (IBM) 1978 State transition testing was introduced by Tsun S. Chow 1976 Cost-of-change curve was introduced by Barry Boehm
- 14. 14 The History ofSoftware Testing Debugging Demonstration Destruction
- 15. 15 Destruction - OrientedPeriod 1979 The book by Glenford Myers is the first book about software testing only. It introduces black box testing. 1981 IBM personal computer goes mass market 1982 The first computer graphic is Disney movie Tron 1982 ‘Life Cycle Concept Considered Harmful’ Daniel McCracken and Michael A. Jackson criticize the waterfall way of software development
- 16. 16 The History ofSoftware Testing Debugging Demonstration Destruction Evaluation
- 17. 17 Evaluation - OrientedPeriod 1985 Windows 1.0 is released 1987 Ivar Jacobson introduces the concept of use cases 1983 The first version of the IEEE 829 Standard for Software Test Documentation is published 1985 AutoTester - the first commercial test tool for PC - is released by Linda and Randy Hayes
- 18. 18 The History ofSoftware Testing Debugging Demonstration Destruction Evaluation Prevention
- 19. 19 Prevention - OrientedPeriod 1988 First edition of ‘Testing Computer Software’ by Cem Kaner 1990 Boris Beizer uses the term ‘pesticide paradox’ 1990 First Internet service provider 1991 Linux released 1992 Rational Unified Process published SCRUM 1993 Jeff Sutherland and his colleagues develop software in Scrum teams 2001 Agile Manifesto published 2002 The International Software Testing Qualifications Board was founded Releases of popular tools 2002 2004 2004
- 20. 20 20 Good to haveskills
- 21. 21 What skills aTest Engineer should have SOFT SKILLS: ● Motivation ● Passion ● Great attitude ● Communication skills ● Analytical skills ● Time management skills
- 22. 22 What skills aTest Engineer should have HARD SKILLS: ● Good knowledge of testing theory ● Basic HTML/CSS knowledge ● Basic knowledge of Database/ SQL ● Basic knowledge of Linux commands ● Basic knowledge of networking protocols ● Knowledge and basic hands-on experience of a Test Management Tool ● Knowledge and basic hands-on experience of any Defect Tracking tool ● Upper-intermediate level of English
- 23.
- 24.
- 25.
- 26. 26 Misperceptions About TheProfession Software Testing is a simple job. So anyone can do it Testing is a second-tier job when compared to development Testers earn less as compared to developers Testing is boring
- 27. 27 Misperceptions About TheProcess Software testing will delay the whole project Testing can only be done when the product is complete Testing is expensive There is no need for manual testing if we can automate
- 28. 28 28 Successful resume forfreshers
- 29. 29 Writing a GoodResume DO’s: • Do a research on the company • Customize your resume and cover letter • Reflect your personality and skills in your resume • Read your resume twice or thrice thoroughly • State your contact information • Provide relevant education and previous work information • List your hard and soft skills in sections • Declare your willingness to learn new skills • Look at other resume samples online DON’Ts: • Apply to a set of positions at a stretch • Blindly apply to the position without even reading the position titles and requirements • Include fake experiences and skills in the resume • Underestimate the impact made by resume and cover letter • Provide a personal email that sounds very unprofessional • Include 20 previous jobs that have no relevance • Write everything in one big paragraph • Say that money is your biggest motivation • Assume your resume is perfect so no need for improvement
- 30. 30 So, what doI include in CV and CL Your resume should include: 1. Contact information 2. Personal statement 3. Soft skills 4. Hard skills 5. Education 6. Work experience 7. Hobbies 8. Languages Your cover letter should include: 1. Date 2. Contact Person's Name, Title, Company, and Address 3. Salutation 4. Opening Paragraph 5. Middle Paragraph 6. Second Middle Paragraph 7. Contact Information and Closing
- 31.
- 32.
- 33. 33 Resources • Prometheus: Думайінакше: Зламай перешкоди на шляху до навчання та відкрий свій прихований потенціал • Prometheus: Основи тестування програмного забезпечення • Prometheus: Основи програмування CS50 2019 • Coursera: The Bits and Bytes of Computer Networking • Prometheus: Основи Web UI розробки 2022 • Khan Academy: Intro to SQL: Querying and managing data Free Courses • W3School: HTML/CSS, SQL • SQLBolt: Introduction to SQL • Guru99: UNIX / Linux Tutorial for Beginners: Learn Online in 7 days • Guru99: Computer Network Tutorial for Beginners Tutorials • ISTQB: ISTQB Foundation level Syllabus • Rex Black and others: “Foundations of Software Testing ISTQB Certification 3rd Edition” • Lee Copeland: "A practitioner's Guide to Software Test Design" • Agile: Scrum Guide • Agile: Kanban Guide • Джеф Сазерленд: “Scrum. Навчись робити вдвічі більше за менший час” Reading
- 34. 34 34 “Believe you canand you're halfway there.” — Theodore Roosevelt
- 35.