How to become a successful quality assurance engineer from scratch?
Introduction to Quality Assurance: A Comprehensive Guide
In this comprehensive guide, we delve into the world of Quality Assurance, starting from the very basics, understanding the importance of practical QA, API testing, and finally automation.
About the Author
Sam Masak is a seasoned Quality Assurance Engineer with over six years of experience. He also holds the position of a Quality Assurance Lead for over three years. Sam has rich experience in several domains, such as mobile testing, web testing, fintech, cloud storage projects, augmented reality, and artificial challenges.
The Role of Quality Assurance Engineering
Quality Assurance Engineering plays a crucial role in building robust and secure software applications and products. QA Engineering ensures maximum usability, functionality, and minimal bugs in the software, ensuring a seamless experience for the end-user. Sam currently works with Exo Incorporation, a software engineering company with a robust QA Assurance Department.
Gender Diversity in the IT sector
Sam shares some interesting statistics about women's representation across different sectors within IT. He shares that women form about 77% in administration, 60% in the Quality Assurance sector, and about 36% in the project management department.
Entering the Quality Assurance World
Entering the world of Quality Assurance requires certain skills and soft traits. You should have a strong desire to learn, be sociable, ready to face difficulties, possess self-analysis skills, and have the ability to admit mistakes.
Essential Tools for Quality Assurance Engineering
- OTRS: It's an open-source ticket request system.
- Jira: A project management tool used for bug tracking and project planning.
- Confluence: A collaborative software program where team members can share knowledge efficiently.
- Google Docs/Microsoft Office Tools: Tools to create documents.
- Dev tools in a browser: These enable you to test and debug your webpage in the development phase.
- Team Communication Software: Tools like Skype and Slack.
Learning Strategy
Building an effective learning strategy is essential. You should start by arranging the topics in order of importance and then work on understanding these topics thoroughly.
Understanding the Basics
Sam recommends referring to resources like the ICTQB syllabus for learning the basic theory of testing. He also encourages learners to apply the theoretical knowledge in practice for better understanding.
Tips for Effective Practice
Practical quality assurance involves tasks like writing test documentation. Select any open source project and start creating test cases for it. The key is to develop a holistic understanding of the project's functionality.
API Testing
API testing is crucial in the QA world. Sam suggests mastering tools like Swagger and Postman for API testing.
The World of Automation
With a basic understanding of HTML, CSS, and Xpath, you can move into automation testing to elevate your QA skills. Tools like Selenium WebDriver, TestProject Framework, and Appium can be extremely useful.
Additional Skills to Develop
Developing excellent communication skills and learning tools for visualization reports, documents, and charts can greatly enhance efficiency in the Quality Assurance field.
Conclusion
Quality Assurance is a vast field with plenty of opportunities for learning and growth. Remember, "if you fail, don't give up when one door shuts another opens." The key is to try repeatedly and continually seek new knowledge.
Frequently Asked Questions
At the end of the session, Sam addressed several questions. Serving as an inspiration to many, his final advice is to explore resources like the ICTQB syllabus, read extensively about every error, and stay persistent on the journey to becoming a successful Quality Assurance Engineer.
Video Transcription
So for today, our Argenta is um few words about me and uh my current company where I work Excel uh introduction, entering the Quality assurance world theoretical basis, uh practice A P testing and automation. So please write and chat some info that you hear me correctly.OK, thank you. So uh a few words about me. My name is Sam Masak. I'm started my career in quality insurance engineering from the last grade of school. So from my own experience, I know what it means to become a security insurance specialist from scratch. Uh My experience, QR Assurance is more than six years uh and more than three years, I'm a QR as insurance lead. Uh I'm a QR trainer and mentor. Uh I have successfully trained at uh nine Acuity Assurance specialists and now they work on different projects. Uh I start my way in geology insurance from mobile testing, then transfer to web testing, mainly fin fintech and cloud storage projects. Also, I work on projects relates to augmented reality and artificial challenges. Uh on almost the full projects I start ation from scratch and build the estimation pro process. Uh So for now I work at an exo incorporation. So exo is a software engineering company with head office in California as it delivers the digital platforms, products and applications our clients uh need to run and grow their businesses.
So, Exetel established it in 1998 has 23 of in the USA Europe and Asia with more than 1200 employees. Exetel produced more than 20 open source projects and more than 25 solutions. Also, the company has ES O certified in exo we have a big QR Assurance Department that use Exo L QR Assurance Practice. The Exo Q Assurance practice uh applies industry best practice to ensure uh that software is developed and released with maximum usability and functionality and minimal backs.
So I suggest getting to know statistics on how many women are in the it sector. I'm using the statistic from XL L Incorporation. So according to receive uh sta statistics, we see that in, in administration, the percent of women is about uh 77%. So in the Q RT insurance sector, the share of women is about 60%. Uh many women that worked in the Q RT insurance sector for few years transferred to the project management department. In the project management department, the percent of women is about uh 36%. So I think we start introduction to our talk about Kouns from scratch. So um uh my goal is uh to share personal experience in organizing the training process in the field of. So testing for people without the professional and educational ground in the it field and tell about my learning experience from scratch. So the key message of my talk is if you have a design to learn, try it, you can do it. Uh My first message is that anyone who wants to try himself in the quality assurance profession can do it. You need to believe in yourself. But the most important thing is to correctly build the learning process so that it is pleasant and is enjoyable. So the second key message is if you fail, don't give up when one door shuts another opens. So my second message is about if it didn't work out in the first time you need try again because the new knowledge opportunities and equities may open up to you.
So the key problem that I want to raise in my talk is how to start learning from scratch without educational professional background in it, how to build the learning process by myself, how to create a plan for learning process. So we're entering into the Q A vault. So what skills do you need to uh have start learning uh quality assurance. So it feels is a strong desire. Next is a sociability, ready to face difficulties, self analyze the skills and the ability to admit mistakes, friendlessness. So the entrant criteria is here a list of requirements that you should follow while entering the vault of testing. So it is the interesting of profession designed to learn something new and persistent in master knowledge and find solutions to problems. So if you have all the skills and uh criteria, I think you can try if you want in the quality assurance sector, um your way. So uh let's talk about uh the s in order to start learning testing based in my experience. The most important thing is a strong instrument, interest and desire to learn. If a person wants to learn and has power to study of test in science that he will succeed in my practice, I know the people who came with the education of an economic account and philology then are so far from the it sector and they succeed because they really wanted to try and they did it.
So if a person doesn't have a background in it education uh or something experience this, there is a high probability that some of the programs and tools that we use and afi and unfamiliar to him or even all the tools are not familiar to him at all because he worked in another field.
So, analysis of tools and skills you need to use on a daily basis as you will be a geology assurance engineer. So the backtracking system and project planning system uh something like Jira, but Zilla Jira is most um favorite tool. So depending on what is used on project, we use Jira, for example, you need to figure it out as a tool that you can register and create your project for free where you can try to create bugs and tasks. So uh this uh opportunity is uh free for some users. So you can try all way for installing Jira as a project. So it's um uh major uh skills that you need to work as a GEO engineer because you will work with this uh tool every day. So uh system for maintaining documentations, this can be a Jira Confluence Microsoft office tools, Google Docs, depending on what is used on the your fu future project. So how to use um you need to know how to use these tools, basic functions, functions that you needed to create documentation. So because in the Q assurance field, you have uh many uh testing documentations that you will create. So you should create the documentation. So the next um stage it's testing tool. Uh Mainly it's a deaf tools in the browser.
You need to figure out with the sections where uh you should see errors, how to locate elements, how to check network console, how to uh make some um information about loading some requests and information on the page. So it's a also a major skill uh assistant assistant pro program. So it's a like short screen, classify. So tools for screenshot, screen video recording or something like this. Because if you will find the bugs or problems or errors, you should um make a screenshot or video, how you can make this error or bug. So uh team communication software, Skype Slack. So I think uh everyone can use this um um application so it will be OK for all of us. Uh So the next uh stage, it's a learning strategy if you learn uh quality assurance uh by self. So you need to build your learning strategy, arrange topics ordered and carries them uh audit order. And next stage is a mandatory deadline. So you should always set approximate deadlines to mastering a particular topic because time frames improve productivity. So after that, if you some, if you learn some topic, uh so you can make a performance review for uh self because uh if you make little testing for yourself on each topic covered after a couple of weeks.
So uh it's something like a test after every topic that you learn. So it will be something like uh I don't know uh good uh initiation for uh check your knowledges after some uh time. So the next stage is a to Geor basis. So uh about jury, I uh have some um advices to you. So a list of selected internet resources that you need to explain the basic well, so you need to find the basic set of resources that you will use to learn as the uh testing theory. So I recommend using the IC TQB syllabus for learning. So uh it will be a good uh book with all um topics, all need information for testing that used in the different interviews, uh interviews in different companies. So it will be something like um main book of testing. So, but you can choose the resource that you think is understandable for you and comfortable for you. So it's uh not be only this book. Yeah. OK. So uh next uh advice the there is no dry theory. So try to try not to just sit and read the syllabus or everything different book. So try to immediately look for how to apply this knowledge and try it in practice since this way, the information is absorbed much better. So uh I think you need to um uh try this theoretical knowledge in practice. So uh try to find some community of like minded people and the mentor with experience in testing uh plan to conduct a small meetups and the schools discuss uh one small topic.
So if you will have a mentor, he will be able to prompt and direct. So it will be very useful for you if you study your assurance um by myself without some courses and without some um uh trainee uh or internship in company. So, and the next advice is a glossary of technical terms. Uh keep such a dictionary. Uh It is very useful, the correct names of page elements, application uh are very convenient and help when writing documentation. Because if the person is out the ground in it. So uh it will be very helpful in all aspects of work for first time. So uh it will be very useful. So the next uh topic, it's a practice. So uh my tactic is to combine theory with practice uh all time, it's work out the skills very well. So it's best to start practice with tasks such as writing small test documentation, such as for example, test cases For some section is a project, you can select any open source project in the uh internet. So it will be OK, it covers uh the development of several skills at once. Uh this equ acquaintance with the project functionality happens like the this exploratory testing. So you will uh meet the project. Uh So you will make the exploratory testing and write these cases. Uh And a person begins to understand what requirements and how the system works. Now plus according to the template, he begins to write these cases, there are two processes in one. If everything meet the requirements, he write these cases and if not hooray, it's a first B.
So uh try to develop thinking that the many moments that we are not exact requirement and the decision on how to do it falls on the shoulders of the team developers usually do as they like and faster. So, but we tester must say, must say that this is inconvenient incom incom ugly that it is not usability. So also it should be noted that finding A B uh because B AC it's a big win for trainee. So I advise them to pay attention to the test design techs and test them on some selected projects. So usually, if the project is still under active development, then bugs the limitation and validation of fields are found very quickly. Usually this is absent altogether. So, um OK, so move to next level. Uh if you are alone, when the basic theory of testing has already been passed and the practice is mastered, you need to move on and you can proceed to the next stages. So I usually recommend starting to learn a P test. Why? Uh because it's a little easier than ation plus, it's a new skill. It improves understanding of the project. If something doesn't work, the testing can make a request and see if the ban has crashed or front end that already increases uh his skill level. So what do we need to master the basic uh proficiency in a potassium?
So you should know what is the request, types of request, types of errors? You need to understand the types of requests and types of errors because because uh it's a ma major knowledge for A P testing. So uh next stage, it's swagger and postman. Uh based on my experience, I begin to explain from the swagger why? Because this is a whole list of requests and you can try how it works simply by entering the data and can get and it answers, see it, you can also see the request model and the like after that, you can go to the postman when you can uh when you go to, when you move to the postman work, so you should know how to set up the environment in postman.
Uh how we start uh setting up the environment, how to get authorization K where is added, how to add parameters, how to fill in the request body with the correct model, how to read the response, understand errors. So uh it's a main knowledge that you need for postman. And uh also you need to know how to write request, how to write authorization request. Um What's the difference, how to write and transfer Hearer's body and how to read the response? So uh it's uh that do you need for the A P testing? So, and our last topic is uh about automation. So after P testing, you can move to optimation testing. So at first you should figure out what is the ash TML CS S uh X pass. It is the locators that need for your eye automation testing. You should know where to, where you can find it or how to create over locators. So the next stage is the Selenium idea and catalon. So I recommend starting uh this automation, your automation way from these frameworks. There are recorders of your actions in the browser and you can learn the mains of the Selenium Webdriver. So also we can uh we, we have the test project framework is the same recording, but for mobile testing for I Os and Android. So the next level is a Selenium Webdriver or selling it. Uh It's the next level because it is a framework for automation, web testing. For this.
You need to start and learn a, a one of programming language and unite knowledges about commons and locators from your previous uh instruments. So, and uh we have the A P A PM means the same frame of sele web driver but but for optimation testing uh but for optimation, mobile testing, so the commons are same but you need to um initialize the mobile devices using the mole or simulators for testing on mobile devices. So also you need to develop additional skills. So uh for to be a successful culture, students engineer, you would develop communication skills and learn uh cool tools for visualization reports, documents charts and more because it's very helpful for your management. So uh my talk is finished.
So if you have some questions, I will be very happy to answer the questions. So yeah, I recommend uh IC TQB syllabus. Uh it's very good uh resource and book for testing. So also I recommend find a good um uh it's resource, uh great code that rule or uh find the whole list of errors for A P testing for or or all errors of request because it will be very helpful to learn, uh, to learn main errors. So, mm, try to find a list of these errors and uh, read about every error advanced. Uh Thank you very much for, uh, viewing my topic, my talk and uh, bye bye.