Quality Assurance for Beginners - Learn Manual Software Testing | Victor Gorinov | Skillshare

Playback Speed

  • 0.5x
  • 1x (Normal)
  • 1.25x
  • 1.5x
  • 2x

Quality Assurance for Beginners - Learn Manual Software Testing

teacher avatar Victor Gorinov, Automation QA and Programming Instructor

Watch this class and thousands more

Get unlimited access to every class
Taught by industry leaders & working professionals
Topics include illustration, design, photography, and more

Watch this class and thousands more

Get unlimited access to every class
Taught by industry leaders & working professionals
Topics include illustration, design, photography, and more

Lessons in This Class

20 Lessons (1h 48m)
    • 1. Promo

    • 2. Introduction

    • 3. What is Software Development Life Cycle

    • 4. What is Agile Methodology

    • 5. Agile Scrum Team Members

    • 6. Types of Testing

    • 7. Learn What is a Bug

    • 8. Learn What is a Test Case

    • 9. Learn How to Create Test Cases

    • 10. What is Black Box Testing

    • 11. What is White Box Testing

    • 12. What is Cross Browser Testing

    • 13. What is User Acceptance Testing

    • 14. JIRA - Project Management Tool

    • 15. Regression Testing

    • 16. Exploratory Testing

    • 17. Performance Testing - Volume and Load

    • 18. When to Start Automating

    • 19. Interview Questions

    • 20. Thank You!

  • --
  • Beginner level
  • Intermediate level
  • Advanced level
  • All levels
  • Beg/Int level
  • Int/Adv level

Community Generated

The level is determined by a majority opinion of students who have reviewed this class. The teacher's recommendation is shown until at least 5 student responses are collected.





About This Class

Start Learning Quality Assurance TODAY!

★★★★★ "This is one of the best QA software introduction courses, the instructor explains the testing concepts clearly and concisely."

★★★★★ "A great introduction to the QA profession for every beginner, great course!"

★★★★★ "Useful, in-depth walkthroughs. Instructor is knowledgeable, genuine and speaks in a calm, paced manner."

★★★★★ "The best course for starting out with testing software. Every beginner QA should watch this."

★★★★★ "Thank you for this useful information! This course is easy, not too fast and not too slow. Everything is explained clearly and to the point. I recommend this course!"

★★★★★ "A good beginner course for someone who is looking for a QA profession. Very nice presentation!! Thanks."


You will learn different ways of Software Testing and everything you need to start your first job as Junior Quality Assurance Engineer.
This course will give you the foundation and confidence to enter the IT Industry.

You WILL Learn:

  • What is a Test Case and how to write a Test Case

  • What is Software Development Life Cycle

  • What is Agile - Scrum and Kanban

  • Different Types of Testing

  • What is a BUG?

  • Black Box Testing

  • White Box Testing

  • UAT - User Acceptance Testing

  • Regression Testing

  • Cross Browser Testing

  • JIRA - Bug Tracking Tool

  • When You Should Move on to Automation

You don't need any experience to start, you will be guided step by step through this course .
You will also get Bonus Materials to help you from the beginning.

This course requires work in the beginning - just like any other thing in life.
But the best thing in the world is when your start making positive changes in your life.
This course teaches you the simplest way to enter the IT field - Quality Assurance!

If You Are Someone Who:

✔  Want to Become Quality Assurance Engineer

✔  Want to learn Software Testing

✔  Want to Change Career

✔  Want to achieve Financial Freedom and Enjoy Life

Get Started Today!

Meet Your Teacher

Teacher Profile Image

Victor Gorinov

Automation QA and Programming Instructor


My name is Victor Gorinov and I am a Software Automation Engineer and Online Instructor.

On Skillshare I'm teaching IT Courses - mainly focused on Programming for beginners and Quality Assurance both Manual and Automation.

My passion is teaching other people on topics I'm knowledgeable about and seeing their results.
I have always been fascinated by the endless possibilities that we have in our time and the opportunity to reach millions of people with a single click of your mouse.

I am currently working as QA Consultant and in my free time I'm teaching people through digital channels. I am also involved in freelancing, affiliate marketing, investing in the stock market, selling private label products on Amazon and more.

I'm pass... See full profile

Class Ratings

Expectations Met?
  • Exceeded!
  • Yes
  • Somewhat
  • Not really
Reviews Archive

In October 2018, we updated our review system to improve the way we collect feedback. Below are the reviews written before that update.

Why Join Skillshare?

Take award-winning Skillshare Original Classes

Each class has short lessons, hands-on projects

Your membership supports Skillshare teachers

Learn From Anywhere

Take classes on the go with the Skillshare app. Stream or download to watch on the plane, the subway, or wherever you learn best.


1. Promo: Hello and welcome to this quality assurance course for beginners. My name is Victor, and I will be your teacher for this course. I have started my career as manual junior key engineer. I have also being automation engineer and consultant for big companies. I have designed this course for anyone who wants to start his career as a quality assurance engineer, which I believe is a great way to start. Your career in this course will go very basic into learn, step by step. What is the software development lifecycle? What is a software scrum team and water the responsibilities of each member? What is agile methodology? What are the different kinds off tasting? What is a book? What is a test case? And how to create this case is what is the difference between white books and black box testing? What is cross browser testing? What is user acceptance tasting? Who is doing what is juror and why we're using it? What is regression testing and exploratory testing? What is the difference between volume and load testing when you should move from manual toe automation tasting in the later stations, I will show you real life interview questions and I will prepare you for your first kid job in there. You and I will also show you three websites from which you can make money with testing. If you're someone who wants to come courting the assurance engineer or someone who wants to enter the field hip goals for a better life, this course is for you. My main goal for this course is to teach you how to start your first job as a key engineer . We'll go very basic and step by step, and by the end of this course, you will be able to apply for jobs for junior manual engineer. I thank you for your time, and I look forward to see you in the first lesson. 2. Introduction: hello and welcome to my course on how to become quality assurance engineer for beginners. In this first video, I want to welcome you to the course. And thank you so much for being here. I appreciate you as my student, and I want to ask you for your review for this course. It's really important for me to hear your feedback to improve my courses. I'm always improving on my courses and trying to make them the best possible for you. So if you have any suggestions and feedback, please leave me a comment. Send me a message. Tell me what you like and what you didn't like in the course in very port. Important for me. Please leave me your review. Thank you so much. One more time for being here. Now, let's not waste any more time and start with the first lesson. 3. What is Software Development Life Cycle: Hello, everyone, and welcome to the course. Once again, I want to start this first lesson by explaining what is the is the L. C. Or software development Life cycle. And the software development Life cycle is a systematic process for building software that ensures the quality and correctness off the software built is the Elsie process aims to reduce high quality to produce high quality software, which meets customer expectations. The software development should be complete in the pre defined timeframe and cost. And basically, the software development Life life cycle is just a process for developing software. And you may be asked this question if you're going toe interview for a junior developer, key engineer, and basically the whole process starts with requirements. And if you're a customer, for example, until you want a website, you're going toe to this company, which is creating websites, and you're telling them that you want to create, for example, this website like you did me. You want to be ableto applaud courses and people towards them and to leave reviews and comments and to be able to purchase from your website. All of these is the requirements. So the customer, the client comes with his requirements. This is the first face off the software development life cycle after you have older requirements from the client and you know what exactly you should be building as a software product. After that, the design faces coming into place, and this is the face where the U A or the U X designer on the front end developers or create are creating the design or how the Web site or the platform is going to look like they're building the design and they're giving it to the client. The client is giving his feedback, and this process may take a while until the client is satisfied with the final version off the design. And the after that, after we have older requirements and the design is created in the client have approved the design. After that, the next face is the implementation. This is where the developers and programmers are starting to coat the the actual software after the coding after the after the some functionality is being developed and this ready for ah, they think here it comes the next face. After the implementation of the software has been done, it comes time for for us a secure engineers or software testers to taste the software or taste the functionality that the developers have been creating. Usually during this face, we find a lot of books or defects, some things that are not the same with the requirements that the client have given us in the body beginning and the in the tasting face, we may give something back to the develop back to the developers, back to the implementation face. When it's ready, it's coming back toe tasting. If it's not okay, we'll bring. Bring it back to implementation. When it's ready, it's coming back to tasting and win. The key engineers testers are saying that everything is okay and dysfunctionality. This product is ready to be delivered to the client. Then we give this product to the plant when when the product is actually created and tested . And it is what the client have Bean asked for in the beginning. Then we give we deliver this product to the client and after that comes the final face, which is evolution or or maintenance. Basically, after these face, we're just making sure that there are no problems in the client care can use Hiss product, and I want to show you another picture, which is basically the same thing. But with other Graf, I want you to I want to make sure that you understand this is very important because this is the foundation. This is how all the all the big companies, the big outsourcing i t companies are working. And you need to know how everything is working, how everything is connected because we're not working alone. We're working in a team always, and you need to collaborate with everybody and to be on the same page so we can deliver the best product possible for the client. And again, the first face, either requirements the client is coming to us in is giving all the requirements and it is giving us older requirements about the product. After that. Ah, the design face start. It's starting. Cantor. The designers are making on the design for the Clanton after he approved the design. Uh, we're starting to create the actual project. This is the implementation face or the coding off the project. This face is done by the developers. After that, we're coming to the tasting. This is our job as a K engineers were testing the product, and if everything is OK and after the product is has been tested and it's approved by us, we're deploying the product of production, and basically the clan can use the product and from the final face is maintenance. We're making sure that everything is working as expected for the next months, and the client can use he's software. This is basically it. This is the software development life cycle, and you need to know this. You need toe. Be aware that you're going to work with other people and who is going to do exactly which face off the development. The final goal is to create the software, which is in line with the requirements that we get in the beginning from the plant, and everybody's going to be happy in the end. So if somebody is asking you this in the interview now, you know what is the software development life cycle? I hope that was useful. Now let's continue with the next lesson 4. What is Agile Methodology: Hello and welcome to this video. Now we're going to talk about agile. So what is agile? If you look for agile software development into Wikipedia, you're going toe. Find something like this. I'm just going to read this for you, and after that I'm going to explain it with my words. Agile software development is an approach to software, the development under which requirements in solutions evolve through the collaborative effort, off off self organizing and cross functional teams and their customers and users and users . It advocates adaptive planning, evolutionary development, early delivery and continual improvement, and it encourages rapid and flexible response to change. The term agile was popular popularized in this in this contact, the term agile was popularized in this context by the manifesto for agile software development. The values and principles exposed in this manifesto word derived from the underpants, a broad range off sort of software development frameworks, including scrum and kambon. So to explain this in a shorter way with my own words, I would say agile is a set off principles and values, and the aim off agile is to create a better software. The actually the aim off agile is to be ready for for changes in tow. Update things to get feedback from the client as soon as we're ready to give something to the clamp so he can give his feedback right away and we can improve things and this is the whole concept off our job. The whole concept is to be Toby agile to be quick, to improve things, to become, to become better and better every day, to live us to deliver software fast so we can get the initial feedback from the plant. And basically, that's the principles and values in order to create better software and to deliver faster software software, probably you have heard of Scrum and Cambon. These are the two most popular frameworks off agile, and I have been working in scrum and Cambon teams and I know are the benefits off off both of them and the The main difference is that in scrum, you're working in into sprints, so basically you have a user story or or remains a functionality that the team is going to create. And um, we're estimating this functionality with store IQ points. And, uh, for example, our sprint is going to be two weeks, which means that we need to create this functionality for two weeks. You have a time frame for which you need to create this and you're working into sprints and teach Sprint. You're delivering something to the client. A small portion off the software is being delivered every week or every two weeks, depending on the length of the sprint in Canberra, you don't have a time frame to deliver something to the plant you're constantly delivering . So you you don't have springs like one week or two week, two weeks. Everybody's taking something from the camp on board as soon as he is ready, working with something else. So if you're a developer and you you have a task, you finish your task. A soon as you're ready with our task, you're going to the board and you're checking wallet. Is that next? Think with the highest priority and you're taking that and start start working on that so there is no time frame. For example, we want to deliver the specific think for one week you're working on something, and when it's ready, your stand starting the next thing which is in line and that this is basically the the difference. I like scrum bitter because you know each day what exactly you're doing and how much time Hefford for it. But both of them are great ways for developing software and the also the base off agile and the the foundation off this methodology toe. To be flexible and toe improve yourself and your team every single day comes with some meeting since some things that have been proven to work well. One of these things is a daily meeting daily stand up meeting with your whole team, for example, what we were doing in my team every morning, 10 o'clock in the in the morning. We're having a daily stand, the meeting and everybody's telling, and everybody's explaining just for one or two minutes. What is he working on? If he have any problems, have any blockers? If he needs help with somebody else from somebody else and what is he? What he did yesterday? What is he doing today and what he's going to do tomorrow? And the the point of this is to give everybody on the same line so everybody knows his colleague. What is he's calling working on and when something is going to be ready for tasting for, for example, so they'll stand up. Meetings are really important and really helping with development, developing software and having a better communication with your team. Another thing. Kiss if you're working, working in on scrum, agile scrum, met methodology or principle in the end, off your sprints or Indians off your week or two weeks, you have a refinement refinement meeting where you are talking with your team. Basically, during these 12 weeks during this print. What what? I have been working good. What he had been working well and you want to continue doing that? What was not working well, what you can improve and if you have any, suggest suggestions for the next week for the next print and how you can make the process better. This is agile, basically in towards making everything better every single day and improving in the delivering faster software, getting feedback and just constantly delivering better and better software in the yeah, there is agile. Basically, you care for daily stand the meetings when you're working, working in agile environment. In the beginning, when your work starting work on the new functionality, you have a planning meeting where you're creating tasks for everybody. So everybody knows what exactly he's going to do this day, tomorrow, the day after tomorrow, how much time he has for this task for the other task. And basically, for the next one week or two, you have a plan, a written plan that you need follow and you need to execute. And this is really helpful because you're not wondering what exactly I'm going to do. You go from, Where should I start? You have a planning meeting where you're talking about these things and making sure that everybody's on the same page. And in the end of the sprint, the refinement meeting when you're saying what went well, what when bet and how to improve the process for the next print. Basically, that is agile set of principles into methodologies, toe deliver, better software and to deliver faster, too, and get feedback from the client in order to improve the software. I hope that was useful. Now let's continue with the next lesson 5. Agile Scrum Team Members: Hello, everyone. And welcome to this. Listen, now we're going to talk about what is a scream team and what is the role off each member in the team? And the scrum team is a collection off individuals usually between five and nine members, could be 10 11 but between five and find is the typical scrum team working together to deliver the required product. And, um, when you were talking about this crime team, we're talking about the the scrum master, which is which manages the scrum process. This may be the project manager. He may do this work or you may have a project major and a scrum master. Also in this crime team there is, ah, developers beckoned and front end developers que engineers. So, uh, if this can be manual testing or automation tasting or both of them, you may have business analysts. This is the person which is taking all the requirements and basically making all the documentation and making sure that everybody understands the business point of view off the product. You may have architect, which is usually this is a really, really senior developer, which is which knows everything about the all the technical things in the technical stock, which is required for the product. For example, if the client client comes only with his idea and he doesn't know which languages are good for this pro product, and he just given idea, the architect is the person who is telling, For example, we're going to use Java for these or C Sharp is going toe to be suitable for this kind of project, and he's developing the framework and all the necessary taken cough things in the product. The product owner is part of the clients clients team. This is a person who is responsible for the delivering off the product until the product owner is responsible for looking after the product for extended period of time and is accountable for achieving product success. So this is the person who is constantly in in touch with the team with stakeholders and is updating everybody on how the the the product has been developed. And I know that this graph may see a little bit no for a little bit off, too much for you in the beginning, so I just want to I have created this file for you. Just tow to have it does. Ah, something a little bit simpler? Eso you may say so. The the scrum team, the team that is developing the product consists usually off a project manager, the person who is managing the project, who is creating all the tasks. All the who's creating the user stories, who is managing mainly everything in the product with contacting the client side of the business owner, the product owner and basically, he said, he's the link between the scrum team and the client Screw muster. This Maybe this role in my previous team was done from the project major. But usually this is the person who is making sure that everybody have everything needed in order to do their job. And there are no problems in the into the development in the problem in the product. The developers this This consists of front end and back, the beckoned developers. Next exchange nears. This can be manual or automation tasting designers. These are the people that are making the design of the project. This is early in the the early into the office after the requirements face, the business analyst is the person who is making sure that every everybody has the right documentation, the right requirements and everybody understands the business logic off the off the product and from the client site. There is a product owner, basically a person who is constantly in touch with the team with the Scream team and is asking how how is everything going where you're making demonstrations into this to this person and showing him what is the progress? And he's basically the person who is responsible from for the product from the client side and we as a cure. Engineers were standing here, and our job is to test the software to make sure that everything is in line with the requirements and were part of this crime team. I hope her that was useful. This is really and say essential. Before we start talking about testing and according to insurance, you need to have a general idea in the overview off how everything is working, what is the process off developed developing software and after that we're going to go deep into the into the quality assurance into tasting profession. But this is really important to to keep on overview off how everything is working because we are not working alone. We're part of the Scream team and the basically, this will help you if you know exactly what role and what part of the team everybody is doing. And if you collaborate with all of your colleagues, it would be much easier for for you to do your job. So I hope that was useful. Now let's continue with the next lesson. 6. Types of Testing: Hello there. And welcome to this tutorial Today we're going to talk about the different types off tasting and the I want to give you the basics here, off the different types off tasting can't we're not going toe dive deep into each one. We're going toe into the later stations. We're going to learn about the most important ones, But the as a beginner, I want you to just know the basics and to hear about different types Types off tasting. Because when you goto interview and went when somebody is asking you, have you ever heard hurt off integration tasting, for example, you can say yes, this is a part of a functional functional pasting and there was done by this person just to have a general overview for the types off they think And, um, the foundation think that I want you to understand that this is that there is two types off tasting in general in general, functional tasting and nonfunctional tasting. Functional tasting is everything related to the functionality? Is this functionality working or not? The non functional testing is related toe not directly to the is the function anti working or not, but is the functionality working fast enough, is it? Ah, a little bit slow. This is the performance part. This is the non functional tasting. So when you're testing the functionality on the looking for for defects into your on, you're tasting If the functionality is working or not, this is functional testing when you're tasting the functionality for being too slow and, for example, not working as expected. When you load the website with 2000 users, this is non functional tasting. I want you to understand the difference once when somebody is asking, you just know this and the functional distinct includes unit testing, which is done by the developers, not by us by by engineers. And we can say that unit testing is testing individual components. Developers are writing unit unit tests to test individual components to see if they're working as expected and integration tasting. It's ah, if you link all of these units together, are they working as expected? Asses a hole, for example. You have think you have been small things that are working fine. The unit tests are covering that. These 10 small things want you notice is covering one thing the second unit taste is covered in the second thing, and the they're these 10 things are working as expected, has a different units and integration tasting is to check is when these 10 units come together. Are are they working as expected when they're integrated? The unit these air integration tests also assistant testing, sanity, testing, smoke tasting interface. They stink regression testing it and accept interesting these air the functional tasting. Again. We're going to talk more about the most important ones in the later stations. I just want you to give a general overview here. Nonfunctional tasting is a performance testing load testing, stress testing, volume testing, security testing, compatibility, testing, recovery testing, usability, testing and compliance testing. There are many, many magnetized types off. They stink, and even more than what we have here are a lot more than that. But you don't need to know everything, especially in the beginning. You're not expected to do everything. For example, when you're applying for a junior key an engineer, you're not expected toe do performance testing, usually performance distinct and security testing their completely different jobs for for completely different types of people. If you're a cure engineer, usually you're you're going to do a za general Que engineer you're going to do this? Case is you're going to execute the manually You're going to do test plant this execution your After that, you're going toe. Decide which test case you're going toe automate. And this is the General que engineer Role toe. To make sure that the software is working as expected, you need to know older requirements and basically you're responsible for the for the quality of the product. But the performance they think, is a complete different think. And people are doing this another job. Sometimes, For example, if you're using J Meter to to see also the security tasting or white white hat hackers, these are also people that can be defined in a different category. So my main point here is that you don't need to know everything in the beginning. I just want to give you an overview toe. I want you to know what are these roles and water these testing different types off tasting doing, And, uh, you need to know that in the beginning, when you apply for a job, you're not expected to know to be responsible for each of these types off tasting. I want you to just to hear about them. Because if somebody is asking you now, you know about these kind of things Is not something completely new to new to you. And when you start working and when you're in a company in a project, you have a better and understanding about about all of these things. Now I want you just know that generally there two types of testing, functional and nonfunctional. And just to hear about all of these things in the later sessions, we're going to talk about some of these kinds off tasting. Now, let's continue with the next lesson. 7. Learn What is a Bug: Hello, everyone, and welcome to this lissome. Now I'm going to explain to you what is a book. A software book. A software book is an error flow failure or fault in the computer program or system that cozy to produce on incorrect or unexpected result, or to behave in unintended ways. The process off finding and fixing books is Trump as debating the debugging and to say it with my own words because I copied this from Wikipedia or some somewhere on the Internet. To be honest, uh, to say we tweet my own words, a book, it just something that is not working as expected. It can be anything if, for example, where I'm expecting this note. Part puts plus plus toe open when I click two times. If it's not opening, this is a book. Everything that is not working as expected is a book. It can be a huge thing, something that causes millions of dollars or something that causes even, ah, human human lives. If we're working in a health company and which is, for example, developing some medical things, this is really, really important, or if we're working for our car company and we're working functionality where the software is for examples self driving car. And there is a book in the software that means that this car can crash and humans can die. So this is really, really important for us to do our job and to make sure there are no books nor no major books or if you're working in ah aircraft company. Yeah, the pressure is really huge because you know that if there is a book, something that is not working right in the into the aircraft into the plane also people can can can be damaged. So this is really, really important. So it depends on the type of project that you're working rather than the book can be really a big, big type off severity or ah, it can be something that is just going toe to cost money to the client. So just to summarize a book is something that is not working as expected. A simple is that if you know, you know a system, you know, the requirements, how something should be working you you do your task. And if the end result is something else, it's not working as a as expected. This is a book, and I want to click quickly show you this article about about the history's most expensive software books. Just to show you what is the impact that can be done by finding books and by doing our job and making sure that the software is he has the necessary quality. And there no major books. For example, this Marina one spacecraft book that cost $18.5 million. So basically there is some Marine spacecraft that, uh okay, let's let's read this this from the beginning at 18.5 milion, the Marina One Spacecraft is the least expensive book on our historical, released in 1962 a programmer incorrectly transcript a crucial formula when writing the spacecraft source. Quote the lack off a single superscript bar coast. The rocket overcompensate is trajectory as it launched, veering dangerously dangerously off its intended flight path. Jinya. So there was a book in the rocket that's a pretty big deal, and it costs the company $18.5 million this is the least expensive book into this list. If we go to the more expensive ones, the oh my God, $96 million. $475 million the most expensive one was $500 billion. So the Y two K book might be the most expensive book since sees the development of computers. Yet many don't stop and think of its coast because the resulting Clark skill computer disasters never happened. So that was a book was, ah, book across multiple types off software that reduced the calendar years in data sets Toby start as the last two digits off the year to save space. In other words, a computer would read 00 and the end of the date as 1900 Note. 2000 That's a pretty big issue. The issue could have Coast major books in government financial, scientific software and more and more headed. He did not being addressed so that there is a huge book Coast think a lot, a lot of money to the governments and a lot of people. But, uh, this is just something that causes money. This is the better type of books. The the worst part is when, as I said, if you're working into the health industry, when it comes to developing developing communications for people or if you're working for Ah, as I said, a car companies something that is responsible for people's lives or airplanes or something like that. It's really crucial toe. Find these books and to make sure that the software is going toe work as expected, because the worst thing that can happen is to somebody to get hurt. We don't want that. And if you're working on a project and on the software that is going to be responsible for people's last, it's a pretty big deal and you want to find these books. I assume that's possible and just wanted to tell you how big the impact this can have. So find your books like I'll see you in the next lesson. 8. Learn What is a Test Case: Hello, everyone. Today I'm going to explain what is a test case. First I'm going to read this description writer, and after that I'm going to explain it with my own words. So but this case is a set off conditions and variables under which a tester will determine whether a system under test satisfies requirements were works correctly. The process of developing test cases can also help find problems in the requirements or design off on application. So basically a test case is a set off steps that you execute in order to to verify the defection. Ality is working or not, and when we start writing test cases in the next station, you will get this even better. But I want to show you this example of a test case. So this is a test case template. Just toe. Get familiar with this with this terminology. After you start writing them and you're right, a lot of these cases you'll just become better and better, and this will become really easy for you. Now don't get don't. If this is really confusing for you in the beginning, this is normal. Don't get frustrated. You'll learn with this course goes with the later stations, and I'm sure that you'll become better and better every day. And you can start your Your work is the que engineer in no time, I am sure. So a test case is ah, conditions just steps that you execute in order to verify that the functionality is working or not. And facility this this case templates. Ah, all of these tips are not necessary. Everybody has a different style off riding this cases. I will show you mind in the next video. But the lead Just check this one. There can be a tests with i d test case I d. This is not necessary and telling you once again taste case summary. Okay, this is the basically Uh huh. No, this is not the name of the this case. Okay, There is ah, related requirement. Prerequisites. This is important. Any prerequisites or preconditions that must before feared prior to executing the test. So some necessary things that need to be executed before the test. For example, if you need a specific version off a browser, you're going to say it here in tow. The pre requisites at this procedure step by step procedure to execute the test. Okay, these are the steps. There's data in the links in he user names and passwords. For example, that you're going to need for the test case. The expected results. Something really important. Expected result off the taste Mandiant The actual result off the test and the status off the taste really important. This can be best or fail, depending off the end result of this You make if created by you, put your name here. Date of creation executed by So this test can be executed from another person. Date of execution and taste environment. Okay, this is the example off the test case. Eso test case Ah. Summary verified that clicking the generate coin bottom generates coins. This is basically the name off the test case. Okay, prerequisites. User is authorized. So before executing the before starting to execute this case first you need to out rice with ah user. And also coin balance is available available. You need to make sure that these two things are done before executing the test. That means the prerequisites after that comes the taste procedure. Basically, this is the best steps. The first thing. Select the coin denomination in the denomination field. I don't know what is this, but this is just the first step of this case. Apparently, second step entered the number off coins in the quantity filled and 33rd step click generate coin. This is a test data. So we're going to enter these things quantities, Okay. And after that, we have expected result. So the thing that should happen is going off the specified the nomination should be produced if the specified quantity is valid. Okay. And a message, please enter. A valid quantity between one and 10 should be displayed if the specified quantity is invalid. So this is the expected result. What should happen and a the end off the test case. The actual results is something that actually happened. This can be the same with the expected result, which means that the taste will pass and the actual result can be different from the expected result, which means that the test will fail. Okay, here we have. In the actual result, If the specified quantity is very the result this is expect okay? And just say that and the state was we here for fail or pass remarks this is a simple test case. Okay. Created by John Doe. Date of creation executed by Jane Doe and date off execution. This can be This can be different dates from the creation date and the person executing the test could be different than the person creating the test. It's really important toe, right, really understandable and simple taste cases because most of the times, uh, other people are going to look your at your test cases after some time has passed, for example, you're working for this project and you right in this case it with cases and you execute them. And the two years after that, for example, you're not working on this project anymore and another person is coming and he want to read , told the documentation to get familiar with the project. He's most probably going to read your test cases. So make sure that you write them really simple, really clear, really systematic. So when another person is looking at them, he can understand what happens. Okay, It's he what we have here, why didn't do this? Case is as far as possible, right? This case is in such a way that you taste only one think of time. This is really important to make them simple. Okay. Do not overlap or complicate this cases Attempt to make your test cases atomic. So basically what I said just now, make them the simple as possible. Ensure that all positive scenarios and negative scenarios are covered. Of course, you're You make sure that you're covering everything language. So right in simple and easy to understand language. Yep. Use active voice instead of Pacey Voice. Do this. Do that. Okay. Use exact inconsistent names. Form feels etcetera. Basically be specific. And so another person can know exactly what he should do when executing your taste case on the characteristics or for good this case accurate. Exact The purpose. Economical, No unnecessary steps off or words traceable, Capable of being traced to requirements. Yes, very important. Repeatable can be used for to perform the test over and over again. And reusable can be reused if necessary. So to summarize this case is just the verification steps that you need to execute. And in the end of the test case, after you execute the tapes, the steps, you have end result. And if this if this result is what you expected the test is passing. If the XP the end result is not what you're expecting from the requirements, then the test is failing. So this case, you just steps that you execute in order to see if something is working as expected. Now, in the next step, I'm going to show you how I'm writing tests. So let's continue with the next lesson. 9. Learn How to Create Test Cases: Hello, everyone, And welcome to this tutorial. Now I'm going to teach you how to write a taste case. This is really important for your career as a cure engineer. You're going to write a lot of test cases, and you're going to execute a lot of these cases, and this is the first tip off becoming a K engineer. It's something that if you develop this habits off, creating really simple this case, it's your Your work is going to be much easier and which maintainable into in the future. So usually you're going to write your test cases into ah project management system like Jura, for example. But I want I want to teach you how to write your test cases from scratch in north, but for example, because if you learn to do this after that, you will be able to write them anywhere. And it will be much easier for you when you hear for template when to get to the system and you have first step seconds that 33rd step and everything is explained really easy. It will be much easier for you to create a this case if you learn how to do how to create this case is now from scratch into note, but later on it will be much easier for you. So we'll create our test case absolutely from scratch from scratch here in North Pat and, for example, and and, uh, let's say that where we want to test a log in page, let's go toe of websites. I am DB, for example. I am db I think you know this website. It's a huge marketplace for movies. And, uh, let's say we want to taste this logging, but also signing after that signing with IMDb. And we want to test this blogging for this sign in form. Okay, so let's go back into the dashboard page and let's open our north. But the first thing that the first thing that I want right he's the name off the test case . So we need to hear if in our mind on overview, what we're going to taste, what will be the expected result? So I want to taste now that with unveiled credentials, I will not be able to logging into the system, So I want to taste it. If if I right here some a fake email, which is obviously not right. And some password, which is not correct. I will no be able tow logging. So let's create a test case for that. So the name off the taste case will be user is not able to log in with invalid credentials . This will be my test case name. Usually you will have, uh, this written into the project management system system. But Tyrell, right here, case thing just toe. Just for you to get familiar with that. After that, uh, we will have some pre requisites. For example, of this is just on example here, um, I need I don't care. Google Chrome late this version, for example. Um, next thing, I will have faced data which will be, uh, use their name and pass fast words that I'm going to use for the test case for years. Their name will be keep you at gmail dot com. And the password will be my awesome boss works after. Let I will have taste steps. Okay. Here. I will give my first tip, which is Goto. I am DVD dot com. No, the first tape will be open. Google chrome. Second step will be Go to that would have a double you That I am db dot com Step three will be So I'm here now the step three will be click on signing. So click on the sign Botham, The fourth step who be okay. So, uh, I want to make sure that you're following me. The first tip. Okay, let's do it from the beginning. First tip open Google from Okay, I'm opening the from second step is goto imdb not come. Okay, I'm going toe. I'm db dot com Third step is click on the sign in bottom. Okay, I'm clicking here. The next step will be click on Sign in With I M D B k I click here, so click on Signed. What was the the bottom sign with imdb? Okay, with time. Deeply. Que After I click here, the next step is to um right the email. So this actually here would be email. So the next tape will beat right this email here. So the next tape will be enter and this email in tow the e mail field. Okay, step number six will be entered. The passwords enter my awesome passwords in the last words fueled and the next tape will be click sign in click Sign Sign. Okay. And after that, we should very fight that the user is not logging with these invalid credentials. So after that, we will have expected results. And after that, we will have actual result. Okay, Sold. Expected result should be You are not able to look in the system. Error message is displayed there. A message for wrong. That's an error message is displayed. Actual results. Okay, take your results. So I'm not ableto logging. So the actual result is I am not able to look in the system Error message is this plate or you can see user So, user, it's not able to log into the system. And here user is not able to walk into the system. So let's go through these taste case one more time. I'm closing the tap and this is the whole test case. Usually I'm I'm putting images here in two. The expected results into the actual result. So it's ah, even more clear and understandable for the person who is reading the test case. So let's execute this test case right now. Usually from the test case name you. You should you should be. You should already know what is going to happen with this test. You should write the name off the test case in a way that when somebody is reading the name of the test case, he knows what is the this test case about and what he's going to paste. So when I read user is not ableto logging with invalid credentials. I immediately know that I'm going to test a logging functionality and I'm going to taste that with invalid credentials. I should not be able to log in. So after the disc, his name? I have prerequisites need to have Google Chrome latest version. Okay, I have this before executing the test case. I have the taste date here that I'm going to need for the test case. And after that, I'm starting to execute the taste steps. The first step is to open Google from Okay, I'm opening the Google from second step Step number two is Goto. I'm Devi not calm. Okay, I'm putting this into the euro. Que step number three click on the sign in button. I click on the sign in bottom. The next step is click on sign in with imdb. Okay, I click on signing with time the B, the next step is enter this email into the email. Fueled I'm doing this. Step number six, enter this passwords into the password field. I'm doing this. Step number seven is click sign in I click signing. Now Expected result is the user is not able to log in the system. Error message is this plate. This is exactly what is happening. I am not able to log into the system with invited credentials. So this test case is passing. They have your actual results. User is not able to look in the system. Error message is displayed, which means that the test results, um, passing or just best. So this is our test case. We're tasting that we're not able to looking with invalid credentials. Another test case, for example, of course, can be, um, user is ableto logging with valid credentials. And, uh, you're going toe have the almost the same steps you're going to open Google from. Go to imdb dot com, click signing button click signing with time DB. After that, enter this email will be a valid email. So really user after that, enter valid password for this user and click signing. And the expected result will be that you're logged in with your email into your password. So you're into your user account. The the actual result. If you're looked into the system after that, then that this case is betting if you're not able to logging with valid credentials, then the case is failing. I hope that you get this and, uh, and now for homework to get better with test case, I want you to write this taste case that I just talked about. That user is able to log in with valid credentials. Make this just like I did it here, step by step with the test date with steps, and in the end, you should be able to logging with valid credentials. This can be for fun for another website or doesn't matter. Just make sure that you have valid credentials and you can log into a website. Make this just practice writing test cases. And if you you can make a test case like this in tow. Note. Pat. Trust me, it will be much easier for you later on when you're using systems like Juror to create your taste case and you have everything systematically put and you just put the steps, the results, the that this result passing or failing. It will be much easier, but do this in the beginning. Make sure that you understand this. Make sure that you can write it like this like this, and it will be much easier for you later on, also into the expect result. In the actual result, put Screenshots, this will be much easier for the person who is executing the test case. Also, when you're writing books, you find the book and you want toe. Explain a book to somebody Toe developer developer, for example, Put screenshots or even short videos explaining what is the taste case where the book about it's much more easier for another person to know. What are we talking about? No practice. This writes a few test cases right in this case that I told you about about the logging functionality that you can walking with valid credentials. Just practice practice this. You'll get better now. Let's continue with the next lissome 10. What is Black Box Testing: Hello, everyone in this video, we're going to talk about what is Black Box? They stink. Black box. They stink. Also known as behavior, clothes books, specification based or I twi tasting. He's a software is a software testing methods that analyzes the functionality off a software application without knowing much about the internal structure. Design off that item off the item that is being tested and compares the input value with the output. Very the main focus in black box they stink. Is the functionality off the system as a whole? So to put this into a simple words, black box testing is testing the functionality. As a user. Just try to look at these like the taste cases that were writing. For example, you have an input field, and, you know, after this input field, what should be the expected result or the output. But you don't know anything about the internal structure about the coat, the actual coat off because the program this is black, both black box testing when you're tasting the functionality off a software, but you don't know anything about the coat, the internal structure. So basically you're giving input to the system and you know what should be the expected output and you're very fight the the output. So this is how you determine if the test cases passing or failing by the the output. The actual result. But you don't know how things are working in the back. It's like a black box. That's why it's called Black book tasting black box testing because you given any input and you know what should expect in the end without knowing what is actually happening in the back of the program. This is why it's called Black Box, because you only know what should be the actual results. But you don't know hell. Things are working in behind. So Black books tasting is testing the functionality off a software like a user. 11. What is White Box Testing: So what is a white box testing a white books? They stink also is known us clear tasting glass box. They stink or structural testing. This is a tasting technique which evaluates the coat in the internal structure off a program. White Books tasting involves looking at the structure off the coat. When you know the internal structure off a product, this can be conducted to ensure that the internal operations performed according to those specifications, and all internal components have bean adequately. X exercised the Buddhists into a simple words again. White books testing is fixed. I just think the internal internal structure off program in the black box testing you don't know what is happening behind behind the scenes. You don't know what is the program actually doing in the white books tasting? It's exactly the opposite. You know the coat. You know what the program is doing in your tasting exactly that. You're testing the internal structure of the program and you're testing if everything is working as expected. Basically, we're tasting the coat off the program and by tasting the court, your tasting, the a lot of things you're tasting the cold coverage, the components tasting unit testing and basically also security tasting. So the different with the difference between black box and white, both books distinct is that in the black box they think you're testing the functionality. You shift input, uh, that you're putting the test, IP and you have outputs so actual results. But you don't know how thinks things are working in the back. The white books, this think you're tasting the internal structure. So in the black books, you're testing out the external structure. As a user, you're tasting the functionality in the white books, distinct. You're tasting the the insight of the program, the internal structure, and you're tasting the coat of the structure. This is the main difference between black books and white box tasting. Now, let's continue with the next lesson. 12. What is Cross Browser Testing: Hello, everyone, And welcome to this lesson in this. Listen, I'm going to talk about cross browser testing and what is this and why you should know about it. So Cross browser testing IHSAA process to test way publications across multiple brothers. It's logical, right? And cross browser testing involves checking compatibility off your application across multiple Browse where browsers and insurers that your Web application works correctly across different Web browsers. This sounds pretty simple, but this is something important that I want to talk about, just for a few minutes to just to let you know about this. Uh, usually, when you work in a project when the client is giving his requirements, he's saying the which browser this application should work, for example, were a company that our employees air using only Google from, and you're were using the latest version off Google Chrome. And this is the browser that we want to use for this application. Our requirements are only for Google from, so it means the discipline. Cation does not require testing with other browsers like Internet Explorer Explorer and Mozilla Firefox and, uh, H, for example, or Opara and safari. This application, his hever requirements. Only these applications have requirements to work. Only with Google from another company, for example, can come and see our employees air using Internet Explorer. And also we're using Mark. Always we have for Apple computers, and we're using safari. So we chef. So we want this application, Toby, working in Internet Explorer and Safari and also we want toe use our application on mobile so this application have to be tested on Internet Explorer on safari. So on mark always and also on Mobile, you need to make sure that it's working as expected on your phone as well, because this is their requirements. And the cross browser testing is something that should be talked about in the beginning of the project, when the you were talking with the client about the requirements and if they say they only need one brother, this is good for you, a secure engineer. But if they want this application to be working five different browsers, you need to check everything case and every functionality that it's working on. Muti browsers platform so on different browsers again, something that you have to be discussed in the beginning with the client in the requirement face. But just just to let you know that sometimes you may need to taste the same things into a different browsers in tow, Firefox into Rome, into Internet Explorer in toe edge, Safari Opara and stuff like that and Mobile also. So now, after we know this, let's continue with the next lesson. 13. What is User Acceptance Testing: Hello, everyone, and welcome to this tutorial. So they were going to talk about you 80. Which things for user acceptance Day stink? So what issues, er acceptance, testing, user acceptance Testing is the process of very frank that a created solution software works for the user, and this may sound very, really easy, but its its not that easy in the real world and user acceptance tests consists off a set off test steps, which verify if specific requirements are working for the user. So to put this into a simple simple where it's, I would say, user acceptance, they think is tasting from the users. From a user point of view, you're logging into the application, and you're tasting like you will do if you were in your home and just trying to see if this site or application is working as expected. But this is not that simple, because there are a lot of things that should happen before the U 80. So, as I told you in the beginning of the off this course first the client comes and is placing his requirements so client needs lead toe his requirements. After that, the implementation off the design after that. The coding after that. The unit testing after that, the integration testing after the system tasting This is our part. As agree engineers were testing the system and at the end off this cycle is coming the acceptance testing, the U. S. User acceptance, testing and in order in order to get to this face this final face, we need to make sure that everything is implemented as expected. Everything is working is expected. Older requirements are met. We have bean testing the system over and over again, and we're so sure that everything is working us. It should be working that we're giving the system to the client here. And we're saying, Cure you have your product. Now you can taste is if everything is working. This is expected. And when the client is testing the the application application, this is basically the d. The user acceptance testing. He's coming hiss. He's tryingto break the system. He's just typing, called kinds of things and just things that really users would do when they're using the application. That's why it's called user acceptance testing because the user is testing the application . The client is testing duplication, but he's acting like on end user and the these air just steps executed in Lord in order to verify tit. Everything is working as expected. Now let's continue with the next lesson. 14. JIRA - Project Management Tool: Hello, everyone, and welcome to these tutorial today we're going to learn what is Jura and Juror is a tool Developed. Developed by Australian company off last season, it is used for book tracking, issue tracking and project management. The name Jura actually comes. It is inherited from the Japanese worth Gojira, which, which means Godzilla and the basic use of this tool is to track issue and books related to your software. It is also used for project management. The Jura dartboard consists off many useful functions and features which make him blink off issues easy. So to explain it in my own words, because this is copied from the Internet, juror is just too, where you can track the progress off your software, the progress off the product and also a to where you have all the documentation. Well, the the requirements about the user stories that up about about the functionalities and also tracking the progress in the books in the software. It's basically the whole project is in the system and you manage the project from there and I have prepared some screenshots here toe show. What exactly is Jura and how it looks like this is Ah, abort a typical board injera and these columns. Here you can modify them. You can have more than these four columns. Usually you'll have to do in progress after that in development after the in testing kinky A and the Final one is done, and the the main concept here is that everybody have a task, and the this one right here, for example, is a task in the comb toe. Do. So it's not implemented yet, and he should be done. So developer comes here and he doesn't have anything to do. He grabs a task from here, and he moves in the dusk in tow, in progress after he's ready when it's here. By the way, Once, when it seemed this column, everybody can see that, uh, this person, it's working on this task and everybody's on the same page. So you know which colleagues air working on what and how much time they're going to spend on this. After that, you're taking the task from here in public, in putting it into a tasting column or ready for tasting something like this. After that, when the tester the curate this is us, we're testing this task and we're moving the task in tow. Done. Usually the process is something like this in your truck. The whole project. Here, let me show you another screen like this to do. After that, you move it into progress after that, Awaiting Q A When the curies taking the task and starting to test the functionality They put the task here in this column in key. And after that done. This is a typical scrum team Jura Dashboard in the last one that I want to show you is this one. This is the back look, This is also in Juror and this is basically you can put your whole project here into the back. Look, you put all the stories with all the documentation or the requirements, all the acceptance criteria. And when you open a user story which is basically a functionality, you can see all the tasks that are related to this user story. It's just assistant to truck your project with simple words, and you open your this user story and you can see all the tasks related to this story. For example, there 10 developer tasks, five k tasks, toe design tusks and, uh, You can see also the test cases that are created. You're creating the test cases into the Jura. They're also linked into the story. You can think of this like it's like one document. And when you open the document, you have everything linked on. It's really easy to track everything into this document, and this is basically how you manage the project. Let me show you the website of the jurors and, uh, how they're showing here basically the same board that I showed you. Now you can plan truck release report everything injury, basically. Ah, here's a release board which which releases are in progress, which are not released, which are released yet, but you don't need to know. And I think about this yet. It's too early for you for a junior, Kate. Um, and you can you can see the Basque Open in progress of the review. Final approval don't basically can modify these columns. Just remember, that juror is ah development tool for tracking for tracking and main. Drink your project and the developers the case. Everybody's is using this tool in order to be in line to know, to know your colleagues to no water, your colleagues working on how much time they're going to spend on something. If something is going to be ready for testing today, tomorrow, basically you're managing the project and everybody's on the same page. 15. Regression Testing: in this video, we're going to talk about regression tasting. So what is regression tasting? Regression? Testing is defined as a type of software testing to confirm that the reason programs or code change has not adversely affected is existing features. Regression testing is nothing but a full or partial selection off already executed test cases, which are really executed to ensure existing functionalities work fine. This that testing is done to make sure that new coat changes should not have side effects on the existing functionalities. It ensures that the old cold steel works one of the new court changer changes are done now . I will try to explain this with my own words and to make it a little bit more simple. So it's pretended to hear if, ah, a program that is working fine and the developers air working on something new that they want to implement in the project. And they're developing this cold for a center, a certain amount of time in the new functionality. Israeli, When the new functionality is is being implemented, toe the already existing project. You want to make sure that the new functionality is working properly and also everything before this functionality is still working properly. So basically, with regression testing your very find it, the old functionalities are still working after the new changes. Basically, that the new coat didn't break the old functionalities. Regression testing is basically executing old this cases and doing old tests to verify that the old functionalities are working after you have made some changes in the project. And it's really useful when you have some alternation here. Because when you have automation tests and there is something new, a new functionalities is being developed. You can run the automation tests, and they're going to tell you if the old functionalities are are still working and this is going to be executed automatically. But even but you can never out meat everything the whole project, so many old testing is always necessary. I just wanted to let you know what is this regression testing? Because you may hear this, you may be asked on interviews. You'll you'll know a lot more than this when you start working, when you get your feet wet and get into the fields into Diet e field. But the for now, just remember that regression tasting is being executed verified that old functionalities are working properly after the the new coat, the new functionalities air being implemented. So you want to make sure that the new functionalities air working, but they're not breaking the old program and everything is working as expected. 16. Exploratory Testing: Hello, everyone in this video, we're going to talk about exploratory testing. So what is exploratory testing first, Like always, I'm going to read something that I copied from the Internet. This is like like the General documentation off the Exploratory Taste Inc. If you search for eating Google, and after that, I'm going to explain it in my own words. So exploratory testing is all about discovery, investigation and learning. It emphasized personal freedom and responsibility off the individual tester. It is defined as a type off tasting where test cases are not created in advance, but testers chick system on the fly. They may know down ideas about what taste before taste execution. The focus off the focus off exploratory testing. ISS more on testing as a thinking activity. Their scripted tasting you design test cases first and later proceeds with test execution. On the contrary, exploratory testing is a simultaneous process. Off test design and test execution all don't all of them at the same time scripted. This execution is usually a no thinking activity where testers execute the test steps and compared the actual results with the expected results. Such this execution activity can be automated and does not require many cognitive skills. Though the current trend in software testing is to push for automation, exploratory testing is a new way of thinking. Automation automation has its limits. So to put it with my own perspective, in my own words, exploratory testing is just trying to find books without having any scripts in mind. You just go into the system and try to break it, just enter the software and try to do anything that comes up, comes up into your mind that you can taste as a corner case. This this consists off anything you can think off. Just go into the system and try anything you can think off to break the system, and I will give you an example with the IMDb I am db dot com pitch, for example, If I want toe this logging page and I don't I I have already executed my test cases, and when you create this cases and execute them step by step. Of course, you think about them when you create the test case. But when you're executing that this case, you're just like your focus is limited exactly to the steps off the test case. So step one. Do this step to do the Step three. Do this and verify the results at the end. But sometimes and I'm seemed saying this from my own experience. I have find a lot, a lot of books when I'm doing exploratory testing just by exploratory testing. I mean, I'm just going into the program and try to break it with anything that concept into my mind . For example, if if I want to taste this logging page without the cases I want to do exploratory tasting first, I'm going to try ranting writing something like this and some symbols like this, and to put some passwords and try to enter, I will try toe put miners in front, and after that, put some email to see if this is going to work. I will try to put only special characters to see what is going to happen. I will try to toe put for example Ah, big kind off character. So I'm going to copy this. I'm going to face this multiple times to see what is going to happen. Just trying to break the system with anything that comes to my mind and this is called exploratory testing. Just trying to break the system and tryingto test the system with anything that you can think off. We don't without having a script, and I have found a lot off a lot of books back doing by doing this because you don't have any framework that say's, There's limiting Q. And you're just trying toe do anything that comes into your mind and sometimes by just clicking and everything and trying to break things. A lot of the times you're breaking things, and this is how you can find a lot of books. And trust me sometimes this is helping a lot. Not everything has to be scripted. Of course, you have to scrimp int scripting to make this case is, but exploratory testing is also very important. Now let's continue with the next lesson 17. Performance Testing - Volume and Load: Hello, everyone. In this video, I'm going to explain what is the difference between voluntary sting and load tasting? So volume tasting is a type off software tasting that is performed to taste the performance or behavior of the system or application under the huge amount of data. Volume Tasting is also cold fluid testing, and it is a type off performance testing. In the other hand, load testing is a type off software tasting that that is performed. There's the performance or behavior of the system under the expected load off. A really, really world low testing is also a type off performance tastic, so they're both type off performance testing. So far, so good a little bit more about violent tasting volume. Tasting is software testing performed to take the system under huge load data data. LOHT data lost. It is they stick during volume tasting in volume tasting clothes. Huge volume of it volume tasting is used to measure the throughput off the system. Volume tasting makes the system capable off real world use. Volume testing saves maintenance cost and volume tastings. Chicks System's response time so low tasting low tasting is a software testing performed to test the performance of the system under riel Life Float data loss is not tested. The ring little tasting in low tasting clothes in loads is customers expect expectations based Lo tasting is used to measure the performance of the system. Though tasting makes the system capable. According to the end user, it doesn't safe maintenance coast and low tasting chick systems performance. And if you didn't understand any of this, I want to explain it just with one or two centers, two sentences with my own words. Try to to remember it like this because I know that it can be a little bit if you're confusing, especially in the beginning. And a lot of people are missing the what is the difference between the two things? So if you didn't understand anything, from what I just read now ignore all of this every and remember it like this. Try to imagine that you're tasting uploads functionality off a website. Your software is a website that you have applauding functionality and you're tasting this volume. Testing will be tasting this functionality with a huge file, so of file with increased size, Vote tasting will be testing the functionality with multiple small files, so volume tasting is applauding. One file with huge file and floor tasting is uploading many small files. For example, 2000 small faults again. Volume tasting is your uploading one huge file, and you're trying to see if the system is going to respond accordingly. If you upload one huge file so you're in place, increasing the for the volume of the file and flow tasting kiss applauding many, many small files were increasing the LOHT. Basically, that's it. That's the difference between the volume and the low tasting. I hope that makes sense and you understand it. I just want to mention this because when you go to the interview, you may be asked these kinds of questions so it try to remember it with the with the except with the applauding example that I just gave you 18. When to Start Automating: Hello, everyone. In this video, I'm going to talk about automation. And when should you move? When should you move from manual toe automation? They think, And the the answer to that is basically, when you have tasks that you did your repeating over and over and over and over again. Then you want to think about automating these tasks than to avoid repetitive work. If you're doing one task 15 times per day and you're basically doing the same things in clicking the same bottles over and over again, maybe it's going to be smarter to automate this task and to run it automatically every single day and to forget about it in the future. But this is just the simple answer. The more comprehensive answer is that not everything can be automated. So it's automation. Something really nice, really cool, something really necessary, absolutely. Automation is the way to go, and the automation is going. This is the future. Everything is getting automated basically, and this is definitely the future. You want to learn automation, but if you don't have any experience in testing and you're just starting out, do you want to learn automation from the beginning, absolutely not. I think you should first start with manual testing, and you should learn the basics. You should learn the basics like rink and the requirements from the client and knowing how the whole process the software development life cycle is working. You should know how to write this case is how to execute this case is, basically, you have to be a really good manual K or manuals tester in the. After that, you can move on without nation. I think you should know should learn automation, but only after we have a really good foundation and understanding off the whole process. So automation is definitely something that you want to learn. It's really powerful to automate tasks in tow. Have them running in the in the back and you just check the results. But what In the beginning, you should definitely learn your basic tasting skills, your manual skills, your understanding of the whole process, and only after that you should learn automation. And, uh, something very important is that automation, uh, cannot be done to every single task. You cannot automate everything. First off, all automation is is it looks. It's something that takes a lot of time. Not everybody can do it. Not everybody has time to do it. Because sometimes in your project you care deadlines. And your client wants this functionality to be done and to be delivered to him as soon as possible. And you have a deadline and you don't have timeto create automation dates. So you're just manually tested. Try us trying your best toe. Do it as soon as possible so you can release toe production in the plant. So the client escapee, if you give more time and you hear somebody that can do automation tests, then you can start implementing implementing selenium, your selenium, you I automation tests. But they take a lot more time and also need not everything can be automated. So automation is the way to go. But first learned your basics, your foundation. And after that, move on to automation. 19. Interview Questions: Hello, everyone. And welcome to this, lissome. I'm really excited that you're being here because this is the end of the course now, and you should be ready for applying toe your first create job and this whole course keep being preparing you for your first K job. So the interview questions will that I have prepared for. You are basically, uh, everything that they told you so far in this course, and I want to ask you these questions now these questions now and to answer them once again because I want you toe, understand all of these and to hear if some kind of answers when you're going to your first job when you're applying for your for job and you're in tow, interview a lot of these questions. Actually, all of these questions I have, Bean asked when I first started applying for K jobs. So I want to teach you how to a handle on interview process and how toe make a good impression on somebody and how to land the job. Was the menu okay, engineer. So, as I said, the whole course is basically a preparation for your first job, But let's do it once again in this video. So the first question that I have put here is what do you know about the software development life cycle and the When they ask you this, you should say what I told you in the beginning of the course that software development Life's life cycle is a process for developing software product, and the first face is coming with the requirements from the client. After that, when you have all the necessary requirements is coming. The design face the U A, or UX designer is creating the designs for the client. And when the client approves need designs, then the implementation face comes. This is the coding face, and the developers are actually creating the product After that. The case K engineers are testing the product, and if they approved the product after that, the software application is is being deployed to the production. That means that the client gets its product, and after that, the team the scrum team is maintaining the product. So something like supporting the product of them to the next six months. This is what the software development life cycle is. Next question is what is a test case again. You shouldn't. You should know all of these things. You can watch the previous stations, but here I just want to answer with we quite quick answers that this is how you're going toe to react in tow and toe. Answer these questions if you're on interview. So what is it? This case. But this case is implementation off piste steps. And when you execute them, your very frank certain functionality. Basically, this case is just a test the steps that you're executing. And in the end of the test case, you're verified that the functionality is working or not working as expected. What kind of testing do you know Here? You should say that they're mainly there two kinds of tasting, functional and nonfunctional. The functional tasting are related to the functions off the product and nonfunctional is related to the performance of the product. Just like a told you in the earlier stations. And here you can. Also, you can also say all kinds of testing that you can think off, for example, unit testing, integration, tasting stress testing, volunteers to grow tasting progression, testing, exploratory, tasting, all kinds of testing. Did you know you can just say one or two words for them. You're you're really going to shine and you're going to look really good. If you say, like 10 10 types off tasting, can you? You can say one or two words about each one of them, and this is for Junior K. Of course you're going to show what is a book. A book is every single thing that is not working as expected. So basically, we have requirements. You know how something should work, how this functionality should work. If there is something that is not working as expected, it's a book. So everything that is not working as expected was the difference between white books and black box distinct with black box testing que shaver input. And you're just very frank, the final, the expected result. But you don't know what is happening in the back of the program. So you're testing the functionality from a user point of view in the white books. They think you're tasting the internal site off the program, so basically are testing the coat. You're tasting the security and you know exactly what is happening behind the seas. What is exploratory testing? Exploratory testing? He's trying to find defects into the system without having a script and the steps to execute your logging into the system and you're trying to break it with everything that comes into your mind. You're just exploring the system and tryingto find defects. What is unity and who is doing? You get these things for user acceptance tasting, and this is done by the user. So after the implementing, off the product after the very verifying the product from the key 18 and after deploying the product, then the user, then the client, the final user can do this user acceptance distinct in Lord in order to verify that the product is working as expected, this is the final face off, the on the off the product development. What is cross browser testing? Cross browser testing is testing the application in different browsers in order to verify that the application is working, as expected in different browsers. For example, Firefox Safari, chrome Internet Explorer and you can also say mobile applications Well, what is the difference between volume and flow tasting? Here? You commission the example that I gave you earlier in this course with the upload functionality, so volume tasting would be increasing the volume off the file. So one huge file with increased size and flow tasting will be many small files uploaded to the system. For example, 23 4000 files about small files uploaded to the system. Can you out meat? Every test case? No automation, something that have to be really carefully thought. And some test cases are just not applicable for automation. Automation is really powerful, too, but you should first do your manual testing. You should know how the application should work, and after that you can decide which these cases should be automated. But not every single test case should be automated. What is regression testing? Regression Testing is verifying that old functionalities are are still working as expected after applauding new functionalities, basically verifying that the system, they're verifying that the new coat is not breaking the old one. What is Juror used for Juror is, Ah, project mangement tool and book tracking tool, and it's used for manage your project and toe, create user stories and tasks basically toe mange the project into truck. The progress off the team. What are you going to do if you find a major defect in the system you're tasting. If I find a major defict defects in the system and tasting, I'm going to report the book immediately, toe the developers into the project manger of the team. So everybody knows about this, and the developers can start fixing the problem as soon as possible. And the project manger can do the documentation if something has to be done related to the client. And after I report immediately to the team on going toe, create a book report explaining everything about the book about the defect, how I how I found the defect going toe touch gree shots. Basically, this question is it's a common sense, but I just wanted to answer it for you because this is something that I have, Bean asked on the interview. And that's it. These are the questions that time belief are more than enough for you to start your first key a job. I'm sure that you are going to do it just fine. These air the foundations off the menu. Okay, Engineer, the junior menu cure engineer. This is a job that allows you to enter the I T field, and we all know that this field is really rewarding and we have a lot of benefits, a lot of perks, good salary into this field. So you can you can become, ah, just a engineer and change your life and change your family's life. That's why I want to help you. I want to to teach you all of these because I was a few years ago, I was working something completely different than the the salary. The salary was not even nearer to the salary that I'm taking a secure engineer. So I think everybody can learn these things. Everybody can apply them. Everybody can find a job and really change his life for a better. So I hope that you learned a lot from this and I was here in the next listen. 20. Thank You!: congratulations for finishing my whole course. Thank you so much for being my student and for being here. I really appreciate you. And I hope that you get the value that you came here for and you learn a lot of new things . I'm sure that if you apply the things that you learned from this course, you can become a K engineer and you can change your life for the better. Thank you. 11 more time for being my student and for being sure. And please give me a review for this course and tell me if I can improve something. I'm always improving on my courses. And I hope to see you in my next course. Thank you. And bye.