About

Careers

Team

<h3>Introduction</h3> During any kind of software development, a Quality Assurance process is required if the code quality is concerned. During any human endeavor, including programming, mistakes (bugs) are unavoidable. So the main task of the quality assurance (QA) engineer, sometimes also referred to as a tester, is to identify and raise issues so that they can be fixed in a timely manner. As software types vary greatly so does the QA processes and tools used to test them. In this course we will take a look on various types of testing (regression, smoke, etc) and learn when and where they are applied. We will also learn how to test mobile, web and desktop applications and identify which tests can be automated and how to go about doing that. <h3>What is BDD and TDD?</h3> In the software engineered world you’ll hear the terms BDD and TDD casually tossed around. BDD stands for Behavior Driven Development and TDD stands for Test Driven Development. TDD encourages writing tests before starting the development of a feature. So at the first run the test obviously fails. After the feature is developed the test is run again and it should pass this time. Consequently, the codebase will have high test coverage which is a good software engineering practice. As you can see TDD is a developer-centric testing approach and used for writing unit tests. BDD on the other hand, describes a feature or a functionality in a human-readable language called Gherkin, understandable to various stakeholders involved in the project. In practice we use IDE plugins to have nicely formatted scenarios in Gherkin and runnable methods in Cucumber for Java or Behave for Python. <h3>QA Basics</h3> Depending on the software under the test different tools and methodologies are used for testing but there are some fundamental testing principles shared among various testing approaches. Let’s learn about those principles. Testing reveals the presence of defects, not their absence No tester can assure that the software on have doesn’t have any issues. Perfection is hardly achievable in real life. Hence, as testers, we do our best to find and document bugs but we cannot say with absolute confidence that the software under test is bug free. Exhaustive testing is impossible Simply put, you cannot test every possible scenario in which the product under test can break. That’s practically not feasible. Also, it doesn’t make sense because you can gain sufficient confidence in performance and functionality of your software by strategically covering with tests the most important aspects of it. Meanwhile, automated testing tools exist that can generate a huge number of test cases thus giving you enough confidence in your tests. <h3>Web UI testing</h3> In web UI testing you, as a tester, try to make sure that the elements on the webpage function properly, are placed correctly, and look as intended. To test the functionality of web elements you would normally try interacting with them like clicking a button, choosing an option from a drop-down, etc and see if they are behaving correctly. The correct placement is easy to check by a visual inspection of the page. Meanwhile, to have a correct look and feel certain CSS attributes should be present. All the described inspections can be done manually though it can be error prone and time consuming, especially if there are many pages to test. An alternative is to automate the testing process by writing tests that can run periodically and perform the mentioned tasks. Arguably the most popular tool for automated UI tests is Selenium but another tool called Cypress is also getting popular in recent years. <h3>API Testing</h3> Practically all modern web and mobile applications make some kind of API calls to the other servers on the web. Via API requests and responses an application interacts with back-end and third-party services to perform various tasks like user authentication, data retrieval, sending notifications and so on. So correctly functioning API calls are crucial for the application's health. Though you can check an API call response on the UI side by trying to log into the system or validate data retrieved from a 3-rd party service, it is faster to test the underlying calls directly. Here’s when API testing comes into play. Commonly used API requests are GET, POST, PUT, and DELETE. Every API call consists of a request endpoint, header and body. The body content is usually JSON or XML. The most popular API testing tool is Postman. It lets us make all kinds of API requests and observe the responses. Some advanced features of Postman include Environments, Scripts, Collections, Mock Servers and more. Besides Postman, we can use special programming language libraries like Python’s requests library intended for working with the APIs. This gives us more flexibility and deeper automation test coverage.

What is Quality Assurance and how does it work?

QA Basics 

<h3>Introduction to QA</h3> During any kind of software development, a quality assurance process is required if the code quality is concerned. During any human endeavor, including programming, mistakes (bugs) are unavoidable. So the main task of the quality assurance (QA) engineer, sometimes also referred to as a tester, is to identify and raise issues so that they can be fixed in a timely manner. As software types vary greatly so do the QA processes and tools used to test them. In this course, we will take a look at various types of testing (regression, smoke, etc) and learn when and where they are applied. We will also learn how to test mobile, web and desktop applications and identify which tests can be automated and how to go about doing that. <h3 style="text-align: justify;">Who is this Course for?</h3> No prior familiarity with QA processes is required to take this Course. We start with the basics and carry on to advanced concepts in the field of QA automation. We assume , though, that you are familiar with basic HTML (for web UI testing) and REST protocol (for API testing). <h3>What is BDD &amp; TDD?</h3> In the software engineered world you’ll hear the terms BDD and TDD casually tossed around. BDD stands for Behavior Driven Development and TDD stands for Test Driven Development. TDD encourages writing tests before starting the development of a feature. So at the first run the test obviously fails. After the feature is developed the test is run again and it should pass this time. Consequently, the codebase will have high test coverage which is a good software engineering practice. As you can see TDD is a developer-centric testing approach and used for writing unit tests. BDD on the other hand, describes a feature or a functionality in a human-readable language called Gherkin, understandable to various stakeholders involved in the project. In practice we use IDE plugins to have nicely formatted scenarios in Gherkin and runnable methods in Cucumber for Java or Behave for Python. <h3>QA Basics</h3> Depending on the software under the test different tools and methodologies are used for testing but there are some fundamental testing principles shared among various testing approaches. Let’s learn about those principles. Testing reveals the presence of defects, not their absence No tester can assure that the software on have doesn’t have any issues. Perfection is hardly achievable in real life. Hence, as testers, we do our best to find and document bugs but we cannot say with absolute confidence that the software under test is bug free. Exhaustive testing is impossible Simply put, you cannot test every possible scenario in which the product under test can break. That’s practically not feasible. Also, it doesn’t make sense because you can gain sufficient confidence in the performance and functionality of your software by strategically covering with tests the most important aspects of it. Meanwhile, automated testing tools exist that can generate a huge number of test cases thus giving you enough confidence in your tests. <h3>Web UI testing</h3> In web UI testing you, as a tester, try to make sure that the elements on the webpage function properly, are placed correctly, and look as intended. To test the functionality of web elements you would normally try interacting with them like clicking a button, choosing an option from a drop-down, etc and see if they are behaving correctly. The correct placement is easy to check by a visual inspection of the page. Meanwhile, to have a correct look and feel certain CSS attributes should be present. All the described inspections can be done manually though it can be error prone and time consuming, especially if there are many pages to test. An alternative is to automate the testing process by writing tests that can run periodically and perform the mentioned tasks. Arguably the most popular tool for automated UI tests is Selenium but another tool called Cypress is also getting popular in recent years. Practically all modern web and mobile applications make some kind of API calls to the other servers on the web. Via API requests and responses an application interacts with back-end and third-party services to perform various tasks like user authentication, data retrieval, sending notifications and so on. So correctly functioning API calls are crucial for the application's health. Though you can check an API call response on the UI side by trying to log into the system or validate data retrieved from a 3-rd party service, it is faster to test the underlying calls directly. Here’s when API testing comes into play. Commonly used API requests are GET, POST, PUT, and DELETE. Every API call consists of a request endpoint, header and body. The body content is usually JSON or XML. The most popular API testing tool is Postman. It lets us make all kinds of API requests and observe the responses. Some advanced features of Postman include Environments, Scripts, Collections, Mock Servers and more. Besides Postman, we can use special programming language libraries like Python’s requests library intended for working with the APIs. This gives us more flexibility and deeper automation test coverage. <h3>Mobile Testing</h3> A popular open-source choice for testing mobile apps is Appium. It doesn’t require including an SDK or recompiling the app. The best part is you can still use the test automation tools you are familiar with like Selenium and it works with iOS, Android, and Windows apps. Both native and hybrid apps are supported. Appium relies on client/server architecture to fulfill its task. The server listens to commands through its REST API method calls, executes the commands on a mobile device and returns an HTTP response that represents the result of command execution. An immediate advantage of client/server architecture for testing is that tests can be written on your local machine. When executed it communicates with a cloud service like Sauce Labs to receive and interpret the commands. This is a more scalable approach as opposed to hosting both client and server on the same machine. The client libraries are written in Java, Ruby, Python, PHP, Javascript, and C# This was the introduction of QA. Nextly we will explore together "Testing tools", "Soft skills of testers" and so on. Keep up with us!

We start with the basics and carry on to advanced concepts in the field of QA automation.

Introduction to QA

<h3>Manual Testing Tools for QA Engineers</h3> Software testing is one of the essential steps on the way to the project release. There are two primary ways of software testing: automation and manual. While each method has its advantages and disadvantages, its main goal is the same: to ensure the quality of the software. Manual testing is the oldest and primary form of software testing. It is the process of testing software application features and functions from an end-user perspective. Unlike automated testing, which uses a software program to conduct such tests, manual testing relies on the actions of a human. Nowadays, in parallel with technology advancement more and more tests are becoming automated across different layers of the application under test. But despite this fact, the art and science of manual testing continue to be critical to software quality for the foreseeable results. <h3>Manual Testing Tools</h3> A wide range of manual testing tools is available to simplify the testing process and keep all tasks organized. Here we have manual testing tools classified by categories: Test Case Management Tools A test case management tool helps organize, measure, report, and collaborate on manual testing projects. Testing usually involves a lot of documentation, and if the right tools and processes are not in place, things can quickly become disorganized. A good test case management tool can make testing a lot easier when it comes to keeping those assets organized and up to date. Suggested test case management tools: TestLodge -TestLodge is an accurate and simple way to organize testing documents. With TestLodge, we can write and manage test cases, requirements, test plans, and test suites. It can also be perfectly integrated with certain third parties to provide accurate reporting results. Zephyr – Zephyr works with Jira to help testing teams to leave spreadsheets behind and improve visibility into their test results. TestLink – TestLink is an open-source test management tool. It pairs requirements with test cases and supports both manual and automated testing. Issue Tracking Tools Another essential manual testing tool for software testers is an issue tracker. As defects are found, testers need to write a good bug report for sending to the design and development teams to work on and fix them. There is a large quantity of issue tracking tools, and while each one is different, they all aim to solve the problem of helping to track issues easily and collaborate with teams on project work. Suggested issue tracking tools: Jira – Jira’s flexible framework with its customizable features makes it one of the most popular manual issue tracking tools for software testers. Operating around Jira is easy, but at the same time complex, depending on the user and the mode of operation. Basecamp – Basecamp is a project management favorite. With a single, all-in-one dashboard for organizing projects, teams, and corporate communications, Basecamp comes in handy with a live chat function, a message area, a to-do list, schedules, and documents, all on the all-inclusive dashboard. It can be used in multiple fields. Trello – Trello is a project management and issue tracker tool that allows testers to create issues on a board. Trello can be set up in a basic form as well as be configured using more complex rules and automation. Asana – Asana is another widely favored work management platform with numerous variations in application and is used by several of the world’s biggest companies. Teamwork – Teamwork is a project and work management tool that can be easily customized to support the way teams like to work. Cross Browser Testing Tools Cross-browser testing tools often involve verifying that the UI elements are rendering correctly across multiple browsers, involves physically checking functionality and how the code responds in each browser. There are many cross-browser testing tools available today that can help testers to save time and effort, and make sure their web applications function properly on each browser. Suggested cross-browser testing tools: BrowserStack – BrowserStack is a widely used manual testing tool. It enables testers to quickly load their application to on-demand browsers and devices, which saves them a lot of time. Sauce Labs – Sauce Labs is a continuous testing tool that offers simple cross-browser testing solutions. Browser Shots – Browser Shots is a free tool where you can load a URL then receive screenshots showing how the site looks on various browsers. API Testing Tools API testing verifies that the API meets expectations regarding the application’s functionality, security, performance, and reliability. The process often involves repeatedly running the same API calls, which can be time-consuming. API testing helps testers expedite this process by saving and organizing frequently used API calls and scripts. Suggested API testing tools: SoapUI – SoapUI helps software testers test APIs more efficiently. SoapUI supports API load testing, API functional testing, and API performance testing. Postman – Postman is an excellent tool for writing and storing API requests for testing. These requests can be executed manually or run in a sequence automatically. REST Assured – Rest Assured is a java library that helps testers to validate RESTful API endpoints quickly. Screen Capture Tools Many software defects are cosmetic flaws or workflow issues that can be better understood visually, so screen capture tools are valuable when testing manually. Some screen capture tools have the facility to call out specific notes by marking up the image. Being able to generate an image or screen recording quickly in this manner helps software testers communicate bugs more accurately. Suggested screen capture tools: CloudApp – CloudApp is a screen recorder, screenshot creator, and animated .gif generator. It allows testers to capture what’s happening on the screen instantly then share it with their development teams. Loom – Similar to CloudApp, Loom also generates screen recordings and videos, allowing testers to record what they are looking at on the screen. Skitch – Skitch enables testers to capture screenshots quickly and annotate them for extra context. Email Testing Tools Email testing is an area that is often overlooked, but it is super important to make sure emails are functioning correctly and look good. Today, with automated emails and smart drip campaigns connected to software, email is just as much a part of the product as the application itself. This is why we’re including these email tools in our manual testing tools list. Suggested email testing tools: Litmus – Litmus is an excellent manual testing tool allowing testers to view how their emails render in different email clients, so avoiding testers having to sign up to numerous accounts and install email clients, thus saving time. Mailtrap – Mailtrap is another practical manual testing tool that email testers love. Mailtrap does the work of a real SMTP server and prevents test emails from mistakenly landing in a real customer’s inbox. Email on Acid – Email on Acid is a multi-featured email optimizing service that includes campaign analysis and cross-client testing for the performance of individual emails. <h3>Conclusion</h3> Productivity, organization, and the overall effectiveness of manual testing can be improved by using a combination of tools. Many of these tools are low cost or free, and will make a positive impact on manual testing workflows right away.

There is a wide range of manual testing tools to simplify the testing process and keep all tasks organized.

Manual Testing Tools for QA Engineers

<h3>Automated Testing tools for QA Engineers</h3> Automation Testing or Test Automation is a process of performing test cases by repeating pre-defined actions using special tools, scripts and software. Once the test suite is automated, no human intervention is required so by this way the number of test cases to be run manually is reduced but even in this case manual testing is not eliminated altogether. <h3>Automation Testing Approaches(frameworks)</h3> Before presenting the list of the most popular and used Automation Testing Tools let’s find out the main types of frameworks in Automation Testing. Data-Driven Automation Framework A data-driven framework separates the test data from the script. Testers can store data externally so setting up a data-driven test framework tester will have an opportunity to store and enter the input/ output parameters to test scripts from an external data source. Keyword Driven Automation Framework With the keyword-driven framework, each function of the application under test is laid out in a table with a series of instructions in successive order for each test that needs to be run. Having a similar style to the data-driven framework in a keyword-driven framework as well the test data and script logic are separated. With this approach, keywords are also collected in an external data table, making them independent from the automated testing tool being used to execute the tests. Modular Automation Framework While working with modular framework testers will have to divide the application to be tested into separate units, functions, or sections, each of which will be tested individually. After breaking down the application into separate modules, a test script is created for each part and then combined to build larger tests in a hierarchical style. A key strategy in using the modular framework is building an abstraction layer so that any changes made in individual sections won’t influence the overarching module. Library Architecture Testing Framework The library architecture framework for automated testing is based on the modular framework but has some additional advantages to mention. Instead of separating the application under test into the multiple scripts that need to be run, similar tasks within the scripts are identified and later combined by function. Linear Automation Framework With a linear test automation framework there is no necessity to write code to create functions as the steps are written in sequential order. Here the tester set each step down such as navigation, user input, or checkpoints, and then plays the script back automatically to conduct the test. Hybrid Automation Framework As the name suggests, a hybrid framework is a combination of any of the previously mentioned frameworks set up to use the benefits of some and reduce the weaknesses of others. As more teams move to an agile methodology, setting up a flexible framework for automated testing is important. <h3>Automated Testing Tools/Frameworks</h3> Selenium WebDriver - According to the “Test Automation Landscape in 2020 Report” 54% of the responders mentioned Selenium as their main automation testing tool. Selenium is one of the leading open-source automation regression testing tools for browser-based website automation. But, Selenium is not a standalone-testing tool. It’s an API that enables us to programmatically write tests using most programming languages to interact with a browser the way a real user would. Selenium offers flexibility to developers and testers who have experience and skills in programming and scripting but to use Selenium effectively, users have to possess advanced programming skills and need to spend much time building automation frameworks and libraries. This is the main weakness of Selenium, which is addressed to other tools built for codeless automation testing tools such as Katalon Studio. Cypress being an extremely developer-centric test automation framework focuses on making test-driven development (TDD) a reality for developers. One of its design principles was to be able to package and regroup everything together to make the entire end-to-end testing experience pleasant and simple. This approach delivers more consistent results since it can easily understand everything happening inside and outside the browser. It also gives native access to every object without requiring to deal with object serialization or wireless protocols. Webdriver IO is an open-source test automation framework based in JavaScript and is built over nodeJs. WebdriverIO has many advantages like its extendability, compatibility, multiple features available, and effortless installation. This is considered a Next-generation test automation framework that supports both desktop and mobile apps. It supports BDD and TDD test framework. Appium is an open-source automation testing tool for mobile, web, and hybrid applications on iOS/ Android mobile and Windows desktop platforms. Appium supports multiple programming languages provides cross-platform (both Android and iOS) testing on real devices. Being one of the leading test automation tools Appium attempts to be an industry standard for mobile testing, much as Selenium WebDriver is a standard for browser-based automation. Robot is a generic open-source automation framework. It can be used for test automation as well as for robotic process automation (RPA). Robot Framework is used in the software development of many industry-leading companies. Robot Framework is open and extensible and can be integrated with any other tool to create robust and flexible automation solutions. Being an open-source automation tool Robot Framework is free to use without any license. Robot Framework has an easy syntax, using comprehensible keywords for testers. Robot Framework is an operating system and application-independent. The framework is implemented in Python but also runs on Jython (JVM) and IronPython (.NET). Golem is a complete automation testing tool and framework at the same time used for end-to-end testing. It creates powerful, strong and stable test suites, yet, it is easy to pick up and learn even without a lot of programming knowledge. Having a complete GUI module (a web application) to write and execute tests,a reporting engine and a web reports module and an interactive console Golem can use the Page Object pattern, write tests with multi data sets (data-driven), run tests in parallel (remotely as well) and test APIs Cucumber is an open-source Behavior Driven Development (BDD) automated testing tool. Cucumber allows us to interpret application’s behavior in plain meaningful English text using a simple grammar defined by a language called Gherkin. Cucumber is written in Ruby, but it can be used to “test” code written not only in Ruby but also written in other programming languages. The focus of cucumber is the end-user experience. Katalon Studio is a powerful and comprehensive automation solution for API (both Soap and RESTful), Web, mobile, and desktop application testing. It also has a rich feature set for these types of testing and supports various platforms such as Windows, macOS, and Linux. Testers who find difficulties in integrating and deploying different frameworks and libraries to use Selenium and Appium, as well as who are already familiar with these engines can choose Katalon Studio as an ideal option that provides uniquely integrated environment. Groovy is the main scripting language used by Katalon and supports external Java library. So it allows us to reuse Selenium scripts written in Java and use directly in the tool. It integrates easily with Continuous Integration systems like Jenkins, Bamboo, and TeamCity. TestComplete - is a GUI test automation tool for Web, mobile, and desktop application testing. Testers can use JavaScript, VBScript, Python, or C++Script to write test scripts.TestComplete has an object recognition engine that can accurately detect dynamic user interface elements. This tool is especially used in applications that have dynamic and frequently changing user interfaces. As a product of SmartBear, TestComplete can be easily integrated with other “SmartBear” products. It also Integrates tightly with the tools such as CI/CD, test management, issue tracking, and version control, giving users a complete testing lifecycle. Ranorex studio is an all-in-one functional test automation tool both for iOS and Android that provides a comprehensive and professional set of features for Web, mobile, desktop, and API testing. Leveraging its experience in desktop-based test automation, Ranorex has advanced functionalities for UI element identification, editing, and management. Ranorex makes automation testing easy for testers with its friendly and simple GUI, record/playback, and script generation. Test Project is the world's first free cloud-based, community-powered end-to-end test automation platform that allows users to easily test Web, Android and iOS applications on all operating systems. <h3>Conclusion</h3> As we can see there is a huge selection of automation testing tools and finding the right testing tool from all the available ones is not easy, so we need to have basic knowledge of each automation testing tool to understand which one could be the ideal option for us depending on specifications of our software and unique needs of our team.

The most popular Automation tools used by QA engineers.

Automated Testing tools for QA Engineers

<h3>How to prepare for an QA interview</h3> <ul><li style="text-align: justify;">QA (quality assurance) being an inseparable part of software development moves forward expeditiously. And, therefore, the position of QA engineer is one of the most demanded roles in nowadays’ Job Market. We see hundreds of job announcements daily for QA engineers and it seems too easy to get a job. But is it so? Being a good specialist and having profound knowledge of QA is not enough to get this role as there is a kind of “ritual” you have to overcome on the way of getting to your dream job. It is about job interviews. An important and indispensable point in any step of your career. The main purpose of a job interview is to show your personal and professional qualities to convince and then prove to your interviewer that you are capable of taking all the responsibilities and risks related to an appropriate position. Here you can find some general advice that can help you to shine in your job interview.Before going to an interview for any role it is necessary to do profound research of the company and position you are applying for. Observe any kind of information about the company’s history, the scope of engagement, production, concurrence, and so on...</li><li style="text-align: justify;">Be self-confident, but note that overconfidence may have a negative impact on your image from the view of the HR or Manager (who takes your interview). So try to avoid an overconfident tone while presenting yourself or answering the questions.</li><li style="text-align: justify;">Talk clearly and comprehensively, don't try to make an impression by using complex and little-known words. It is important that your interviewer gets everything you are talking about, otherwise, It is most likely that your speech will be interrupted by him/her and you will risk failing your interview and lose the chance to be hired.</li><li style="text-align: justify;">Talk without rushing, neither too fast nor too slowly not to lose your audience.</li><li style="text-align: justify;">Never talk negatively about your previous job/team/management. It is one of the most common mistakes during a job interview that will ruin your reputation in the eyes of your interviewer instantly.</li><li style="text-align: justify;">Do not be egocentric, even talking about your experience, skills or education try not to keep you in the center all the time, it will not be seen positively from the side of your interviewer. </li><li style="text-align: justify;">Do not forget to use your body/gestures. In such a situation using body language is highly desirable. </li><li style="text-align: justify;">As it is your first meeting with your recruiter your speech may not be enough to make a good impression on him/her and here body language comes to aid you. Just use the right gestures and manners. So the chance that your interviewer will be convinced is increased automatically.</li><li style="text-align: justify;">Prepare questions to ask your recruiter at the end of your interview.</li></ul> Most frequently asked question in an interview for QA engineer 1. SDLC/STLC SDLC (Software development life cycle) consists of the following steps: requirement analysis; product designing; product building; product testing; product deployment in the market and maintenance. STLC (Software testing life cycle) consists of the following steps: requirement analysis; test planning; test case development; testing environment setup; test execution; test cycle closure. 2. BLC Saying BLC (Bug life cycle) we understand the line of statuses every bug can go through during its “life”. The main bug statuses are: new; assigned; open; fixed; tested; verified; closed; reopened; duplicated. 3. Testing levels Every software under test must pass the following levels of testing to be fully acceptable for release: unit testing; integration testing; system testing; acceptance testing. 4. Positive and negative testing Positive testing is done by providing valid data as an input and then checking whether the software behaves as expected. During negative testing, invalid or improper data is provided as an input and it is expected to get appropriate errors regarding invalid data entered. 5. What manual testing tools are you familiar with? This is when you should present all the manual testing tools you have worked with. 6. What automation testing tools are you familiar with? This is when you should present all the automation testing tools you have worked with during your previous projects (if any). 7. Some types of functional testing. Functional testing refers to activities that verify a specific action or function of a software. Functional testing types: unit testing; regression testing; integration testing; smoke testing; recovery testing; sanity testing; interface testing; system testing; user-acceptance testing. 8. Some types of non-functional testing. Non-functional testing refers to those aspects of the software that are not related to a specific function or user’s action. Non-functional testing types: security testing; usability testing; reliability testing; performance testing. 9. Difference between Scrum and Kanban. Scrum and Kanban have many similarities, but they are different in their principles. Working with Scrum means having the whole testing process divided into little intervals called “sprints”. There are clearly defined test stories to be done by the end of each sprint. Sprint duration needs to be defined in advance (before starting the testing process) by the team and it is always the same for every sprint. In the case of working with Kanban, there are no sprints or such intervals for the testing process. All the tasks that need to be completed by testers are located in a storage called “backlog”. Testers are free to prioritize and choose tasks to do. 10. Validation, verification Verification is a static process that starts from the first stage of SDLC and goes to the phase of “testing”. It is mostly about checking documentation and product design, observing specifications and requirements to understand whether the process is going in the right way, as expected. Here we don't have code execution, code is checked but no action or execution is done. Validation is a more dynamic process done in the phase of “testing’ by the QA team to be sure that the product meets the needs of the customer. 11. “Black box”, “White box” testing Black box testing, also called “blind” testing is done to test the behavior of software from an end-user perspective. When using “black box” testing methods, you don’t have any access to software code. Unlike “black box” testing, “white box” testing implies mostly technical testing to check the internal functioning of the system. In this case, the tester has access to the main code to better understand the logic and specifications of the modules. Having excellent technical knowledge is good but not enough. To be a fully competitive candidate you need to own some personal qualities every recruiter pays much attention to. So, to find out your characteristics requiters move to some general questions that help to reveal your “inner self”. <h3>General questions asked during a job interview:</h3> <ul><li style="text-align: justify;"> Why are you applying for this position?/ What attracts you the most in this role?</li><li style="text-align: justify;">How did you learn about this position?</li><li style="text-align: justify;">Where do you see yourself in five years?</li><li style="text-align: justify;">What contribution do you imagine bringing to our company in the first three months of your work?</li><li style="text-align: justify;">Which are your strengths and weaknesses?</li><li style="text-align: justify;">Which are your salary expectations for this role?</li><li style="text-align: justify;">Why should we hire you out of all other candidates?</li><li style="text-align: justify;">How do you imagine your dream job?</li><li style="text-align: justify;">Describe the best working environment for you.</li><li style="text-align: justify;">Which is your biggest dream?</li><li style="text-align: justify;">Describe yourself in 3 words.</li><li style="text-align: justify;">What/who motivates you in your life? </li></ul>

Here you can find some advice from us that can help you to shine in your job interview.

How to prepare for an QA interview

<h3>Soft Skills for QA engineers</h3> It is not a secret that every specialist no matter in which sphere, needs to possess some soft skills besides the hard ones required. Soft skills reflect your emotional intelligence and ability to interact with your team members, thus define how successful you are/will be in your team. That is not something you should just list in your CV but something you must demonstrate in your work. As we have already talked about Manual and Automation testing tools in our previous articles let's now discuss the SOFT skills for QA engineers. Below we have the list of the top five soft skills every QA engineer must have to succeed in his/her career: Communication skillsNo doubt that communication is an essential part of the working process of every QA engineer. Note that here we are talking about both oral and written communication. As a software tester, you need to communicate effectively with your team (including both technical and non-technical personnel) so that you could easily understand each other. Especially communication with Developers is crucial because the main purpose of QA engineer’s work is to find bugs and then have them fixed by developers due to their proper communication skills. So, any non-healthy communication between QA engineers and Developers may lead to the failure of the mission and unfixed bugs will be the result of that. Any unfixed bug in its turn is a source of “danger" for the entire system. Time Management skillsTime Management skills are essential for any employee. According to recent researches, time management is one of the top five most demanded soft skills. Good time management implies the following skills: multitasking, prioritizing, scheduling, appointment managing, delegation, planning, etc. In other words, it is the ability to manage your working time productively and efficiently and, therefore, meeting all your deadlines, keeping your working process organized and systematized․ The key point in time management is the focus, as jumping from one to another task may affect your productivity and cause stressful situations for you. Attention to detailsAnother soft skill that every QA engineer must own is attention to detail while accomplishing tasks, observing documentation, requirements, or product specifications. Being a detail-oriented employee means having the ability to allocate your cognitive resources to achieve absoluteness and accuracy when managing your tasks. Identifying even a minor bug in the software under test may have a serious trickle-down effect on the entire application. So, don’t ever underestimate the importance of being detail-oriented at your work. Fast-learning skillsThe IT industry is in constant growth and development. To stay a competitive specialist you have to be extremely up-to-date with all business needs and tendencies. You must be ready for any challenges like learning (relatively) new tools or approaches required by your management or your clients. It is impossible without your strong ability of fast learning, flexibility, and stress resistance. In addition to fast learning skills, we can mention researching skills as well, because in most cases you must have to find your needed information on your own and it may demand special skills. Confrontation skills / Strong characterBeing a QA engineer requires a strong ability to stand up for your point of view even if no one is on your side. You need to own solid confrontation skills to controvert, negotiate, and finally persuade your interlocutors to listen and take your opinion into account. Otherwise, you can not succeed and grow in this sphere. <ul><li style="text-align: justify;"> </li><li style="text-align: justify;">Other soft skills also important for QA engineers: Proactivity</li><li style="text-align: justify;">Creative minding</li><li style="text-align: justify;">Analytical thinking </li><li style="text-align: justify;">Problem-solving skills </li><li style="text-align: justify;">Decision-making skills</li><li style="text-align: justify;">Team playing skills </li></ul>

The list of the top five soft skills every QA engineer must have to succeed in his/her career.

Soft Skills for QA engineers

<h3>What other tools should QA engineer know ?</h3> Besides the main Manual and Automation testing tools which we have already talked about in our previous blogs, there are some additional tools QA engineers may need during their working processes. So, It would be highly preferable for QA engineers to be familiar with the following tools: CI/CD tools Azure DevOps is a Software as a Service platform․Being a leading continuous integration tool is used by the support team while deploying and building applications. Azure DevOps includes a range of services you can choose based on your requirements and business needs: Azure Repos that provide Git repositories, Azure Pipeline that supports continuous integration and delivery of the application, Azure Boards that support work planning and tracking, Azure Test Plans that provide app testing tools, Azure Artifacts that provides package sharing options. Jenkins is an open-source continuous integration service mostly used during job runnings. Jenkins is especially popular for its wide range of plugins. Plugins make Jenkins a unique and valuable service to use. Jenkins enables developers to build and test software continuously. So, with Jenkins, users will always have the freshest builds of the software as changes are integrated to the project easily and fastly. Circle CI is the world’s leading continuous integration and continuous delivery platform. CircleCI provides users the fastest job runs. CircleCI integrates easily with Git Hub/Bitbucket, and every time the code is committed a new pipeline is created by CircleCI. Then pipeline runs automatically to test the commit, and if any failure is found team is notified about it. Git Lab CI/CD is a service supporting all the integration methodologies: continuous integration, continuous delivery, and continuous deployment. During continuous integration small part of the code is pushed to the main codebase of the software located in a Git repository and with every push scripts’ pipeline runs to build, test, and validate all code changes before having it merged into the main code. Continuous Delivery and Deployment suppose one more further step. Application is deployed to production with every push. These methodologies allow finding the bugs in the early stages of development. TeamCity is a Java-based continuous integration server and build management tool proposed by JetBrains. TeamCity is a commercial tool and licensed under propriety license. Database management tools MySQL is the world’s leading open-source database management system. MySQL databases are relational, which means that data is stored in separate tables instead of being kept in one big storage. MySQL databases are very fast, scalable, and user-friendly. Oracle RDBMS is an all-in-one relational database management system used to create and manage databases. With Oracle, users can safely store and retrieve the data. Oracle database has some structural features which make it one of the most popular database management tools: logical data structure, memory caching, data dictionary, backup and recovery, clustering. PostgreSQL is an open-source object-relational database system. PostgreSQL runs in all operating systems, supports almost all types of data (image, text, sound, video, etc). Postgre supports four standard procedural languages ( PL/pgSQL, PL/Tcl, PL/Perl, and PL/Python) and allows users to write their code on one of these languages and then execute it by Postgre database system. MongoDB is a cross-platform, document-oriented database system used to store and manage a large amount of information. Mnogo DB is classified as a NoSQL (Not Only SQL) database system. Test case management tools Test Rail is a web-based test case management tool giving users the ability to create test cases and test suits, execute test runs and track the results. It is not only used by testers and developers but also by team leads to organize, manage and track and software testing process. Test Lodge is a cloud-based test case and project management tool. It provides a simple way to create, manage, execute test cases, then track the results. Besides test cases and test suits, here we can write and manage test plans as well. Being a cloud-based tool, Test Lodge supports almost all browsers and operating systems and easily integrates with multiple other tools. Documentation management tools Confluence is an incredible workspace (corporate wiki) for teams to share knowledge and collaborate dynamically and effectively. Confluence is created in Java programming language and published in 2004 by Atlassian (an Australian software company). FlowShare is a documentation management tool used to create step-by-step, precise instructions and detailed documentation quickly and easily. With FlowShare it’s also possible to transmit software knowledge, organize some onboarding processes, create support experience, and so on. ClickHelp is a browser-based documentation management tool intended to create knowledge bases, useful/help files, professional tutorials, and FAQs for the staff. It’s easy to use as there is no installation needed, and it supports all the possible platforms: Mac, Windows, Linux. Swagger is a set of open-source tools for designing, building, and using Rest APIs. This set of tools includes Swagger Editor, Swagger UI, Swagger Codegen. These tools help to create client libraries, generate interactive API documentation and enable users to make API calls directly in the browser. Bit.ai is an all-in-one document management and collaboration platform. Here we can create both internal and client-facing documentation. Every user has the permission to update and edit available information, add new recourses and documents.

Additional tools QA engineers may need during their working process besides the main tools used.

What other tools should QA engineer know ?

<h3>We are Tesvan!</h3> A company providing quality assurance services for local and foreign companies since 2019. This article is not about our work and services but mostly about our team. So keep reading and explore the life of Tesvanners behind the doors of the office. Your 3 words best describing the Tesvan team. Lusine: “Casual, Supportive, Flexible” How we work As we are a QA Օutstaffing company we have multiple projects we are working on. Generally, there is a person or a pair in charge of each project, and due to our good collaboration skills, we always succeed in working in pairs. Based on project specifications we work on multiple QA frameworks using different tools. Tesvanners are familiar with most of those tools but there is always one tool each of us is the best on: like saying API testing we imagine Ara, Lusine is our Git guru, Selenium masters are Arman and Norayr, Vazgen is unstoppable in mobile testing and so on... One of the strengths of Tesvan is that we all are good both in individual and team work which makes our team flexible and effective. And to keep a good work ethic there are some key points which must be strictly followed: time management, responsibility, and excellent communication skills. How would you describe Tesvan in 3 words? Ara: “ Yellow, Happy, Smart” How we learn and grow Working in the IT-sphere means growing continuously. We realize that for being competent and valuable specialists in this field we need to improve our skills and knowledge. We give much importance to self-development and self-improvement which are especially enjoyable when accompanied by teamwork. And how do we do that? For every month we suggest several topics related to IT or software testing and each of us chooses a topic closer to him/her and explores that deeply in order to prepare a presentation for other teammates. So, at the end of the month, we do a line of presentations. We gather together to listen to each other, share our thoughts regarding the topic, ask questions and find the answers together. It is a good approach to learn new things and grow which has become a habit for us! What can’t you imagine Tesvan without? Levon: “Laptops and warm smiles of my colleagues :)” What we play It’s not only work that unites us, but also our hobbies! Where to go without Tesvan games and teambuildings? Nowhere! The first on the list is Football, as we all are big fans of football, even the newcomers who didn’t express any interest in it in past, become involved with that just in a very short period of time. We like watching matches and then discussing our favorite moments, rewatching epic goals and sharing our emotions at the office. Sometimes Tesvan boys organize football matches and play with other teams. Also, we never miss the chance to watch football matches from the stadium, it is another pleasure for us. And a good occasion to make good memories all together. What do you like the most in Tesvan? Mane: "People!" After football, the second place is for chess. Once or twice a month, we organize Friday “Mafia Night”, after work. We like playing any new and interesting intellectual games, doing debates taking global topics. Almost every month we organize one teambuilding, or a camping activity to fully relax and be recharged with energy. What is missing in Tesvan? Merine: "My favorite coffee “Jacobs”, instead of “Nescafe”, more fruits especially mandarins for winter, and a perfect internet connection :) " So, Tesvan is not just an office, where we work and spend 8 hours of our day. It is a big family, where we live and grow, support and motivate each other to overcome any difficulty and to become better versions of ourselves day by day. Now, you can get the answer to the question “What is behind the doors of Tesvan?” There is only love, respect, and sympathy! P.S. “Success is a Team Sport!!!” : the phrase always rolling in our mind!

Read and explore the life of Tesvaners behind the doors of the office.

Everyday life of Tesvanners

<h3>How to choose a GOOD laptop</h3> We are usually talking about QA basics, testing tools, skills, frameworks and approaches, but… what if you have faced a case to choose a good/powerful laptop suitable for your work and have some lack in knowing how to do that? This useful article is special for you, keep reading! While taking your first steps in the IT field you will probably face the case of choosing the right laptop with good parameters․ We have prepared a guideline to help you choose a good laptop. Follow the steps: <h3>The Processor</h3> Here we are dealing with two main brands: Intel and AMD. In the Core brand of Intel chips, after the name "Core" you will find a brand modifier, such as i3, i5, i7, or i9. The higher the modifier, the higher the CPU performance and capabilities. When buying a laptop with an Intel processor, focus on models with i5 and higher modifier. As for laptops with Ryzen processors, which are not so many in the Armenian market compared to Intel, in this case, we recommend choosing models with AMD Ryzen 5 or a high index. Processor model Here we must pay attention to the generation of the processor, in case of intel processors, it is highly recommended to buy a laptop with at least 10th generation. In case of Ryzen, at least 5th generation. Processor’s generation is identified by the first/first two digits of the four-digit / five-digit number mentioned in the processor model, such as AMD Ryzen 5 5600H (5600, therefore we have here 5th generation), or Intel Core i5 10210U (10210 in this case, we have 10th generation). The core of a processor, which is an important point as well must be at least 4. Then, one more indicator that is included in the processor model is the product line suffix, which is expressed in letters: G1, G7, H, U, Y etc. What does each of them mean? G - Includes discrete graphics on the package G1-G7 - Graphics level (processors with new integrated graphics technology only) H - High performance U - Power efficient Y - Extremely low power F - Requires discrete graphics Considering all this, it is necessary to understand which type you need to then make a choice accordingly. Of course, it is recommended to buy a laptop with H type processor, but their price is quite high compared to others. <h3>The Screen</h3> Size: 13.3 inches (33.8 cm), 14 inches (35.6 cm) 15.6 inches (39.6 cm) 17.3 inches (43.9 cm) Depending on what you usually do, the purpose for which you use the laptop, you can choose the size that suits you best. A 15.6-inch screen is generally considered to be the optimal size, but if you are a graphic designer, for example, it may be more effective to work with a larger screen. So, this is more a matter of preference. Screen resolution If you are a programmer or QA engineer for whom screen resolution is not a priority, then choose at least full HD (1920 x 1080). Matrix display type: TN- (low image quality, low viewing angle, poor color gamut) avoid buying computers with this matrix type IPS - (high-quality image display, large viewing angle) we recommend choosing models with this type of matrix VA - intermediate position between TN and IPS <h3>The Memory</h3> RAM The next important point to consider when buying a computer is, of course, the RAM, on which mostly depends the capacity of the laptop. We recommend choosing models whose RAM will be not less than 8GB (preferably higher - 12GB, 16GB, etc). By the way, most of the models have the possibility of increasing the RAM that means you can buy a computer with 8GB of RAM, later doubling it to 16, thus paying less than costs any other model with the initial 16GB of RAM. So when buying a laptop, pay attention to this fact as well. While choosing between DDR3, LPDDR3, LPDDR4, DDR4 processors always choose DDR4 or if you want to save some money choose its energy-efficient version LPDDR4. SSD/HDD hard disk We recommend giving your privilege to laptops with SSDs (512GB or larger memory capacity), as in this case the capacity and efficiency of the computer are obviously higher. HDDs, being relatively older information storage devices, are considered vulnerable and slow. Note that SSD in turn has its types: SATA, PCIe, M.2, U.2 each of which has its own characteristics and differs from the others by its price:) For more details: https://www.tomshardware.com/reviews/ssd-buying-guide,5602.html <h3>The Graphics</h3> Integrated graphic card / Discrete graphics Like in the case of processors, here as well we are dealing with two major brands: Nvidia's Geforce and AMD's Radeon graphics discrete cards, for example: Extremely low productivity GeForce 920M, 920MX, 940M, 940MX: Radeon R5 M330, R5 M430, 520, 530: Low productivity GeForce MX110, MX130, MX150, MX230, MX250, Raedon 540, 540X Medium productivity GeForce 1050, 1050Ti, Raedon RX 560X: High productivity GeForce 1650, 1060: Extremely high productivity GeForce 1070, 2060, 2070, 1660Ti, 1080, 2080: <h3>The Ports</h3> When choosing a computer, pay attention to the models that have at least 1 USB-C, at least 1 USB-A, HDMI, and microphone/headphone connection capability.

We have prepared a guideline to help you choose a good laptop.

How to choose a GOOD laptop

<h3>QA and software testing trends in 2021</h3> Accordingly, the QA/Software testing industry has to be extremely flexible to be able to integrate into all those new tendencies fastly and easily. As a result over the years, QA/Software testing industry has changed a lot and there are new working technics and trends which are adopted by QA services provider companies to keep up with the times. Before this article, we have only talked about 2 main testing types (Manual testing and Automation testing) to have a general idea of the QA industry. Now, it’s time to go a bit deeper and explore more! Among those testing trends, we can mention Cybersecurity testing, Codeless automation testing, Big Data testing, Blockchain testing, Security testing, Game testing, AR/VR testing. Tesvan as a QA service provider would like to share with you all the knowledge and experience gathered working in this industry. So, now let’s go through each part and discuss them a bit in detail. <h3>Cybersecurity/ Cybersecurity testing</h3> Cybersecurity, also called IT security is the procedure of protecting essential systems and vulnerable information from any kind of attack (hacking). Ensuring full cybersecurity means having a security strategy that would be able to cover all the below layers: - Critical infrastructure security, - Network security, - Application security, - Cloud security, - Information security, - End-user education, - Disaster recoveryTypes of cyber threats Generally, cyber threats can be categorized as: - Cybercrime: also called computer crime, includes illegal actions such as fraud, stealing identities, or Internat violence. - Cyberattack: usually involves information gathering for political reasons - Cyberterrorism: often intended to generate massive panic of fear Common cyber attacks - Malware: Malware is malicious software created to break or damage a user’s computer. - Ransomware: is another kind of threat that locks down files, data, or systems. Can make private or sensitive data accessible to the public. - Phishing / social engineering: phishing scams, emails, or text messages are meant for gaining sensitive information of a company, such as login credentials or credit card data - Insider threats: insider threads could be presented by the current or former employees or any person who has access to the internal system and all data. - Distributed denial-of-service (DDoS) attacks: A DDoS attack aims to crash the network by generating artificial traffic - Advanced persistent threats (APTs): Here an intruder penetrates a system and remains uncovered for a long time and steals sensitive data. - Man-in-the-middle attacks: It is an attack, where the hacker makes connections with two parties (the victims) and sends messages between them to make them believe they are communicating to each other and thus steal data. There is no doubt that cybersecurity testing is essential. Because even if you are a small or a medium-size business you have the same risk to be attacked as the other bigger and more powerful companies. Cybersecurity testing gives us to understand where especially are our vulnerabilities and what kind of action do we need to reduce any risk regarding our cybersecurity, So, instead of waiting for attacks to fight with then better be proactive and avoid all possible negative scenarios. Being proactive means arranging the right and periodical testing procedures. We can mention 2 main forms of cybersecurity testing: - Penetration testing - Vulnerability testing Generally, the process of cybersecurity testing consists of the following steps: - Cybersecurity audit - Cybersecurity risk assessment - Penetration test - Red team assessment - Bug bounties <h3>Codeless automated testing</h3> Nowadays in the world of automated testing, many companies deal with tools and frameworks that require less or even no code. Here we face the following terms: low-code, no-code, and codeless. In fact, low-code, no-code, codeless, and scriptless terms just explain the same phenomena. It means dealing with tools that will allow users to create and execute tests without having any code under their hands. This approach will allow testers to create a test visually just based on any type of business logic which will make the software testing process much more accessible and easy for those who don’t have any coding skills. But even choosing codless automated testing coding knowledge may be needed to perform specific or more complex interactions. At the end of the day testers and QA engineers ARE NOT developers and they don’t have to know to code as good as programmers do. And which are the main benefits of codeless automated testing? - It reduces time-wastage - Software functionality can be evaluated and tested easily, without creating tests - It is more cost-effective than traditional automation testing - Tests are maintained and scaled easily Top codeless automation tools: - Katalon Studio - Leapwork - Ranorex studio - Selenium IDE - Perfecto - AccelQ <h3>Big Data testing</h3> Big Data Testing can be defined as the process of checking and validating the proper functionality of Big Data Applications. Big-Data gains its fame through its superiority in handling multiple formats of data which the traditional data processing units fail to handle. The data formats which that big data can handle are as follows. - Structured Data - Semi-Structured Data - Unstructured Data The General approach of Big Data Application testing involves the following steps. 1. Data Ingestion Data is first loaded from source to Big Data System using extracting tools. The Storage might be HDFS, MongoDB, or any similar storage. Then, the loaded data is cross-checked for errors and missing values. 2. Data Processing In this stage, the key-value pairs for the data get generated. Later, the MapReduce logic is applied to all the nodes and checked if the algorithm works fine or not. A data validation process takes place here to make sure the output is generated as expected. 3. Validation of the Output At this stage, the output generated is ready to be migrated to the data warehouse. Here, The transformation logic is checked, the data integrity is verified and the key-value pairs at the location are validated for accuracy. <h3>Blockchain testing</h3> Blockchain is a software architecture that has the potential of growing and being a protestor in the industry. With time, with the continuously growing of blockchain systems, we face parallelly the risk of quality issues. So blockchain testing is an unavoidable procedure, which demands high attention and resources. While doing blockchain functionality testing its important to be focused on the following points: - Block Size - Chain Size - Data transmission and - Adding a block Top blockchain testing tools: - Ethereum Tester - Brownie - Truffle - Embark - Drizzle - BitcoinJ - Ganache <h3>Game/Vidoe game testing</h3> What is game testing? Game testing is one of the essential phases of the game development process. Its main purpose is to check whether the game is ready to be launched or not. In other words, Game Testing is a software testing process done to ensure testing and quality control of video games. The main goal of Game testing is to identify and uncover any possible defects and bugs in a video game and thus improve its quality and stability. Game testing represents a step in the game development process that helps to ensure the video game to be distributed is bug-free. Game testing VS Software testing 1. Game Testing Is Complex: It is not easy to be a game tester, because it has a lot of complexities. To ensure quality, Game Testing requires more concentration, diligence, and attention to detail. 2. Software Testing requires Automation: Unlike Game Testing which expects mostly manual effort, software test cases utilize some automation processes as well. 3. More Teams involved In Game Testing Projects: Because of all the manual effort concentrated in Game Testing, the process usually requires more hands. Software test projects may use fewer human recourses as most of the operations can be automated. Besides a software tester can be engaged in multiple projects concomitantly. However, conditioned by the demanding role of each team member in Game Testing, they cannot be requested to handle multiple projects simultaneously. 4. More Teamwork In Software Testing Projects: If we compare Software and game testing processes, in forts one there is evidently more teamwork than on the second one. Usually, software testers work in a team, thoroughly collaborating for getting expected results. Whereas for game testers there is no need for so much interaction with other teammates. 5. Software Testing Requires More Expert Knowledge: As many processes should be automated there is a need for good specialists with profound knowledge of current QA trends and tools, in other words, to be an expert on their work. As for game testing here, each team member of a Game Testing project is generally required to be focused on a particular angle in the game only, thus is no need to master an enormous number of tools. Game Metrics in Game Testing every tester must know DAU/MAU: (Daily active users/monthly active users): This shows the proportion of users who play every day over the number of monthly active users. Session: Each time a user opens the app, that measures as a session. Download Rank: This shows the rate of the game in an app store recording monthly downloads. Retention: To calculate this matrix we different the users into units based on the day the application was downloaded. Performance metrics: This matrix shows the performance of online games. <h3>AR/VR technology testing</h3> Augmented reality (AR) and Virtual Reality (VR) are some kind of “bridge” connecting digital and physical worlds. Due to AR/VR, we can take any information and content visually, in the same way, we can take them in the real world. AR enlarge immediately the ways our devices can help us with everyday activities like searching for information, shopping, or even expressing ourselves. And VR lets us experience what it's like to go anywhere — from the nearest crossroad to any other planet. Why do we need AR/VR testing? First of all, we need to make sure that AR &amp; VR app operates flawlessly across devices and platforms as well as ensure that UX and UI are user-centric which is an important point here. Ar/VR testing is done also to protect sensitive user data from any possible cyberattack. And finally, testing helps to understand all the strengths and weaknesses of the product and help easily find the aspects which need to be improved. The main testing approaches for AR/VR testing - Cross-platform testing - Interactivity testing - Usability testing - Hardware testing - Performance testing - Security testing To get good results: - use real devices in the testing process - involve interactive teams - not only find and fix the bugs but uncover the path to a better product <h3>Conclusion</h3> So, as we can see to stay competitive in the QA industry, software testing companies need to stay updated on the trends and new techniques that will be hazing up in the market. The more flexible they are the higher their productivity is, which will lead them to more prospective collaborations and projects. Tesvan can be surely considered a competent and flexible QA service provider because we are open to any new testing trend. Our specialists are ready to easily integrate new testing approaches and properly respond to the market demand.

Day by day new tendencies and techniques appear in the IT sphere. Let’s now go a bit deeper and explore them.

QA and software testing trends in 2021

<h3>Tesvan is in African market now</h3> Tesvan started its route in the sphere of QA by positioning itself as an Armenian QA outsourcing and outstanding service provider company (here is the blog telling about us) collaborating mainly with foreign companies. In the first year of our activity, we were mostly concentrated in the EU market, collaborating with different companies from Germany, Spain, the Netherlands, etc. Then, we started expanding our geography by creating reliable cooperative relationships with companies from Grece, Ukraine, Russia, and Israel. Over time getting excellent feedback from our client companies we realized that our company has the real potential for growth and development. We are extra-motivated to set new goals to achieve them and that leads us to conquer new heights by striving for new destinations. So, we are happy to announce our next destination which is Africa. This means from now on Tesvan is actively cooperating with African companies providing high-quality Manual and Automation QA services and hope to have a long-term and successful working relationship with them. We already have our first African client company. Here the scope of our responsibilities covers: <ul><li style="text-align: justify;">API testing with Postman </li><li style="text-align: justify;">Version control by Bitbucket </li><li style="text-align: justify;">UI testing using Java and Selenium </li><li style="text-align: justify;">Framework creation and integration with Jenkins CI/CD platform</li></ul> This is only the beginning, we are in continuous growth and process!

We are extra-motivated to set new goals, leading us to conquer new heights by striving for new destinations.

Tesvan is in African market now

<h3>Recommendations on how to drive business value from Test Automation</h3> It is not a secret that our modern world is rolling to automation. There is a tendency to automate (if possible) actions that have been done manually all over time. But why? What makes us starve to automation? The answer is that automation is beneficial for business growth. But how to reap as many benefits of automation as possible? In this article, we will talk about test automation, and reveal its benefits. Here are our recommendations on how to drive business value from Test Automation! 1. The first and crucial point is the GOAL setting Nothing in this world is done without purpose. So, all the objectives need to be clear and precise. Otherwise, the company will have a financial loss and other consequences like the inconsistency of requirements, missed deadlines, and so on. In order to set clear goals for your business, you need to first understand what you want to achieve. Another point that needs to be strictly defined is of course the timeline. For every step that we take we set goals with a specific completion deadline. Note, that the more realistic deadlines you have the more successful your business processes go. 2․ Understand the capabilities and skills of the staff. The work should correspond to the skills and knowledge of the team members. If there are no specific requirements for automation tools, you are free to choose any of a large number of tools. But how to make the right choice? The key is to understand and estimate the capabilities of the team members who should handle test automation. There is no need to always follow the latest tools and approaches, to do experiments... It is important to choose the tools that best match the skills and knowledge of your employees. This way you can save your time and avoid many undesired episodes for your business. 3. The third point is regular maintenance. No matter what kind of business we are talking about, maintenance is a point with an undeniable important role. We need regular maintenance to evaluate the effectiveness and efficiency of each process. We need this to ensure that everything goes as expected and nothing interrupts the workflow to go smoothly. Without this phase, we risk having failures and harmful situations from a business perspective․ 4. Leave some space for manual testing as well․ Even though test automation makes QA engineers’ life easier by decreasing the human factor, there are cases where manual testing is unavoidable. In many cases, manual testing can’t be replaced by automation because of its specifications and nuances. So don’t try to automate the full testing process, not always it is preferable and effective for your business. 5. Define and set a clear Test Data management strategy․ To test the software, testing teams need to prepare and manage the necessary test data, as well as the activities related to it. If the essential test data is not available or well defined, it may cause a negative impact on the overall process of software testing. So you need to be sure that all the data is clearly defined and accessible to the team. The usual process to make the testing environment as close to the production environment as possible is to clone the production data and mask out any sensitive data. 6. No Sense In Automation Unless The System Is Fully Stable․ Any experienced AQA will tell you that before embarking on testing automation you should make sure that your app behaves consistently and it’s robust enough to avoid tests failing at random steps. Reproducibility is key in testing. Hence, if tests can fail due to incomplete code or some other external factors then the system is not yet ready for automation.

Here are our recommendations on how to drive business value from Test Automation!

Business value from Test Automation

<h3>Tesvan Projects by Business fields</h3> In Tesvan we are QA outsourcing service providers taking over about 30 projects in various business fields (more about it later in this article). Our engineers either handle each project on their own or work in pairs. We highly encourage pairwork. In the opinion of our management, it is a practical approach for employees and the company. What kind of projects does Tesvan team deal with? Financial, Blockchain, Gambling, AR/VR, Managemental, Telecommunication, Legal, and so on… Every project has its specifics and nuances. So each of them requires an individual approach and unique work techniques. To succeed, testers need to dive deep into a project, understand the main business logic, clearly envision all the workflows. Only after that, they would embark on their main responsibility: organizing and maintaining the testing process. Moreover, each engineer must be capable of taking responsibility for the corresponding project, be ready to take all the challenges and possible risks. At this point, we have adopted the following approach: Tesvan’s management seeks to know each employee as well as possible. It is done to discover each employee’s strengths and weaknesses, interests, and passion. Why? Because it will help us to choose the right person for every new project. Fortunately, we have only good experience with the aforementioned. With our flexible team and reasonable managerial approach, we always succeed! Now, let’s talk about our projects per their business lines. <h3>Blockchain</h3> Entering a new “world” called blockchain was a little challenging but extremely interesting for us. To be able to handle the testing process, we had to explore this domain deeply and gain much knowledge. First of all, we needed to get acquainted with cryptocurrencies, crypto-wallets, and other related stuff like p2p protocols, smart contracts, Proof of Work (PoW), etc. To implement the blockchain testing, we were provided with a local blockchain, which gave our QA engineers better flexibility and freedom. Lusine: I like trying myself on different projects and discovering new horizons for me. So, I started working on a blockchain testing project, knowing that it would be something new and challenging for me, but I couldn’t imagine that it would be so interesting. <h3>Finance and Insurance</h3> We have several big projects in this sector. Those are different applications with different specifics but with one shared aspect: these kinds of applications are very complex both for development and testing. So, the testing of financial applications requires an extremely detail-oriented and analytical approach. In the scope of testing, our engineers also deal with important procedures such as anti money laundering and anti-fraud inspection. Those actions have huge importance from a business perspective, as they are meant to prevent all kinds of illegal activities posing danger for the company and country’s economy as a whole. Merine: Even the scariest algorithms seem easy if you do you work with love! <h3>Gambling</h3> Another interesting and provoking area where our team has an experience. Gambling platform testing is not easy, it requires experience, skills, knowledge of the latest technologies and tools. Talking about gambling industry testing: we were engaged in online games testing, especially for Sports betting and Online Casinos. We provided full testing that covered all the following points: Compatibility Testing, Functional testing, Localization testing, Penetration testing, Performance testing, Payment testing, and Usability testing. Arman: Yes, the overall process was interesting. The biggest challenge I have faced was understanding the main logic of the gambling system. There was a nice dynamic that pushed me to learn and discover more and more. To the question, “Is there a risk of getting attracted to such games and starting playing them?” My answer is unequivocal: NO. Honestly, I have never been interested in such games. And now, already experienced in gambling testing and understanding how these platforms function, I can surely say that this is something that can never attract me as a player. But testing… yes. With pleasure! <h3>Telecommunication</h3> We have handled the testing of a large project for a telecommunication company. Here, one of the challenges was the fact that we had to deal with microservices, which are more complex compared to monolithic applications. It is also a very responsible and important area. Testing required consistency, a flexible mindset, and lots of technical skills. Telecom testing suggests also working with huge databases and prioritizing data security. Our QAs did their best to handle the testing process as expected and even better! Andranik: I just would like to say one thing. Don't underestimate little, daily things. You can't even imagine how much lies behind a simple SMS you receive every time topping up your balance! <h3>AR/VR</h3> Let’s close the list with another interesting but not less challenging testing experience. AR/VR technology testing may seem complex and scary at first sight. But, it is far from the reality, if you are a real gadget geek. To succeed in this testing, testers should be passionate about new technologies, have out-of-box thinking, and be ready to have a learning attitude. Here, the key is to understand what we are testing. What is it designed to do? If it is clear, everything goes smoothly! Ara:I was excited to be engaged in a team doing AR/VR testing. I dived into the application and just enjoyed the working process. While working on testing, I have also learned a lot of nuances that I would hardly find elsewhere. We can’t cover all our projects in only one article… So keep up with us and read about our other projects in our following blogs!

In Tesvan we are QA outsourcing service providers taking over about 30 projects in various business fields.

Tesvan Projects by Business fields

When working on this project, what were the testing services we provided?

VINETI 

EM Solutions

Indeed

ArctX

Toyota Dubai Mall Store

Vicoland

Mysterium Network

Thetaray

Slidecamp

Etisalat

Fleet Management

Radio Rentals

Amzel

Funkgeraete

Billidoo

Staffidoo 

BimBim

LegalAtoms

Sgames

Flyerdeals 

alfabank

Alfa-Bank

Admarketplace

Ardeo

Bwin

CLOUD PCR

IQVIA

Clustercontrol

SUMMERIZE

Rocky Mountains

Customertimes

<h3>What is QE?</h3> Quality Engineering consists of analysis methods and the development of systems to ensure products or services are designed, developed and manufactured to meet or exceed the customer’s requirements and expectations. Quality Engineering encompasses all activities related to the analysis of a product’s design, development and manufacturing processes for the purpose of improving the quality of the product and the production process while identifying and reducing waste in its many forms. Quality Engineering methods and tools are often developed and implemented using a cross-functional approach involving multiple business and engineering disciplines. Quality Engineering encompasses a broad range of methodologies and tools including but not limited to the following list:<ul><li style="text-align: justify;">Creation, implementation and management of the Quality Management System (QMS)</li><li style="text-align: justify;">Application of Advanced Product Quality Planning (APQP) tools, such as Quality Function Deployment (QFD) and Failure Mode and Effects Analysis (FMEA), from the initial design concept to the manufacturing and monitoring of the finished product</li><li style="text-align: justify;">Integration of the VOC into new product designs and processes</li><li style="text-align: justify;">Working with internal and external suppliers to ensure materials, components and assemblies meet the design and quality requirements</li><li style="text-align: justify;">Identification and elimination of waste in manufacturing and business processes</li><li style="text-align: justify;">Implementation and monitoring of process controls such as Statistical Process Control (SPC)</li><li style="text-align: justify;">Development of appropriate tests and inspections to ensure that process controls are effective</li><li style="text-align: justify;">Working with customers to resolve any quality issues through application of Root Cause Analysis (RCA) and Problem-Solving tools such as 5 Why, 8D, Cause and Effect / Ishikawa diagrams etc., and implementing effective countermeasures to prevent the issue from re-occurring Quality Engineers are the front-line forces for developing, implementing and maintaining the various quality disciplines within the world of Quality Engineering. They are professionals who have gained a thorough understanding of quality principles and product and process evaluation and control. Quality Engineers are normally responsible for developing, implementing and maintaining the systems used to measure, monitor and control product and process quality in the production process. They work with design teams and manufacturing teams to institute quality standards for products and their associated production processes. Quality Engineers must understand process capability and the use of SPC in monitoring the manufacturing processes. In addition, they often define the parameters and develop appropriate end of line testing including setting acceptable limits for the results. Furthermore, the Quality Engineer must be well versed in the use and application of problem-solving tools, troubleshooting, and process improvement. A Quality Engineer must be able to discover and understand the process issues and develop effective countermeasures including process or product changes when necessary, to ensure that quality standards are upheld and the customer’s requirements and expectations are met or exceeded. The benefits of Quality Engineering are vast and can have a profound effect on product quality, process efficiency, and overall customer satisfaction. If you would like additional information about how Quality Engineering methods and tools can positively impact your organization, please contact one of our professional staff at Quality-One.</li></ul> <h3>What is Software Testing?</h3> Software Testing is a process of verifying a computer system/program to decide whether it meets the specified requirements and produces the desired results. As a result, you identify bugs in software product/project. Software Testing is indispensable to provide a quality product without any bug or issue. <h3>What is Quality Assurance?</h3> Quality assurance can be defined as "part of quality management focused on providing confidence that quality requirements will be fulfilled." The confidence provided by quality assurance is twofold—internally to management and externally to customers, government agencies, regulators, certifiers, and third parties. An alternate definition is "all the planned and systematic activities implemented within the quality system that can be demonstrated to provide confidence that a product or service will fulfill requirements for quality." <h3>Quality Assurance Stages:</h3><h3 style="text-align: justify;"> </h3><ol><li style="line-height: 1.5; text-align: justify;">Check product requirements</li><li style="line-height: 1.5; text-align: justify;">Risk assessment</li><li style="line-height: 1.5; text-align: justify;">Planning product quality improvement ideas</li><li style="line-height: 1.5; text-align: justify;">Test scheduling</li><li style="line-height: 1.5; text-align: justify;">Analysis of test results </li></ol> <h3 style="text-align: justify; line-height: 1.5;">Quality Assurance VS Quality Control </h3> Quality assurance and quality control are two aspects of quality management. While some quality assurance and quality control activities are interrelated, the two are defined differently. Typically, QA activities and responsibilities cover virtually all of the quality system in one fashion or another, while QC is a subset of the QA activities. Also, elements in the quality system might not be specifically covered by QA/QC activities and responsibilities but may involve QA and QC. <blockquote>Useful Links: <a href="https://www.youtube.com/watch?v=goaZTAzsLMk" target="_blank">Software Testing/video tutorial/eng</a>&nbsp; <a href="https://www.youtube.com/watch?v=FS_TuKTsYOg" target="_blank">QA Engineering/video tutorial/arm</a> <a href="https://www.guru99.com/all-about-quality-assurance.html" target="_blank">Quality Assurance/article/en</a></blockquote>

What is Quality Assurance and why do we need it?

Quality Assurance

<h3>What is Software Testing?</h3> Software Testing is a method to check whether the actual software product matches expected requirements and to ensure that software product is Defect free. It involves execution of software/system components using manual or automated tools to evaluate one or more properties of interest. The purpose of software testing is to identify errors, gaps or missing requirements in contrast to actual requirements. <h3>Why is Software Testing important?</h3> Software Testing is Important because if there are any bugs or errors in the software, it can be identified early and can be solved before delivery of the software product. Properly tested software product ensures reliability, security and high performance which further results in time saving, cost effectiveness and customer satisfaction. Testing is important because software bugs could be expensive or even dangerous. Software bugs can potentially cause monetary and human loss, and history is full of such examples. <ul><li style="text-align: justify;">In April 2015, Bloomberg terminal in London crashed due to software glitch affected more than 300,000 traders on financial markets. It forced the government to postpone a 3bn pound debt sale.</li><li style="text-align: justify;">Nissan cars recalled over 1 million cars from the market due to software failure in the airbag sensory detectors. There has been reported two accident due to this software failure.</li><li style="text-align: justify;">Starbucks was forced to close about 60 percent of stores in the U.S and Canada due to software failure in its POS system. At one point, the store served coffee for free as they were unable to process the transaction.</li><li style="text-align: justify;">Some of Amazon's third-party retailers saw their product price is reduced to 1p due to a software glitch. They were left with heavy losses.</li><li style="text-align: justify;">Vulnerability in Windows 10. This bug enables users to escape from security sandboxes through a flaw in the win32k system.</li><li style="text-align: justify;">In 2015 fighter plane F-35 fell victim to a software bug, making it unable to detect targets correctly.</li><li style="text-align: justify;">China Airlines Airbus A300 crashed due to a software bug on April 26, 1994, killing 264 innocents live</li><li style="text-align: justify;">In 1985, Canada's Therac-25 radiation therapy machine malfunctioned due to software bug and delivered lethal radiation doses to patients, leaving 3 people dead and critically injuring 3 others.</li><li style="text-align: justify;">In April of 1999, a software bug caused the failure of a $1.2 billion military satellite launch, the costliest accident in history</li><li style="text-align: justify;">In May of 1996, a software bug caused the bank accounts of 823 customers of a major U.S. bank to be credited with 920 million US dollars.</li></ul> <blockquote style="text-align: justify;">Useful Links: <a href="https://www.youtube.com/watch?v=goaZTAzsLMk" target="_blank" style="font-size: 16px;">Software testing /video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=Xx1lRYj_NsY&amp;list=PLRs8EELOYKc7DYIQixlV1s4EH5SR3TdNB" target="_blank" style="font-size: 16px;">Software testing /video tutorial/rus</a> <a href="https://www.guru99.com/software-testing.html" target="_blank" style="font-size: 16px;">Software testing /article/eng</a> <a href="https://www.guru99.com/software-testing-introduction-importance.html" target="_blank" style="font-size: 16px;">Software testing /article/en</a> </blockquote>

What is Software Testing and why is Software Testing important?

Software Testing

<h3>7 Principles of Software Testing</h3> <ol><li style="text-align: justify;">Testing shows presence of defects</li><li style="text-align: justify;">Exhaustive testing is not possible</li><li style="text-align: justify;">Early testing</li><li style="text-align: justify;">Defect clustering</li><li style="text-align: justify;">Pesticide paradox</li><li style="text-align: justify;">Testing is context dependent</li><li style="text-align: justify;">Absence of errors fallacy</li></ol> Exhaustive testing Yes! Exhaustive testing is not possible. Instead, we need the optimal amount of testing based on the risk assessment of the application. Defect clustering Defect Clustering which states that a small number of modules contain most of the defects detected. This is the application of the Pareto Principle to software testing: approximately 80% of the problems are found in 20% of the modules. Pesticide Paradox Repetitive use of the same pesticide mix to eradicate insects during farming will over time lead to the insects developing resistance to the pesticide Thereby ineffective of pesticides on insects. The same applies to software testing. If the same set of repetitive tests are conducted, the method will be useless for discovering new defects. To overcome this, the test cases need to be regularly reviewed &amp; revised, adding new &amp; different test cases to help find more defects. Testers cannot simply depend on existing test techniques. He must look out continually to improve the existing methods to make testing more effective. But even after all this sweat &amp; hard work in testing, you can never claim your product is bug-free. To drive home this point, let's see this video of the public launch of Windows 98 You think a company like MICROSOFT would not have tested their OS thoroughly &amp; would risk their reputation just to see their OS crashing during its public launch! Testing shows a presence of defects Hence, the testing principle states that - Testing talks about the presence of defects and doesn’t talk about the absence of defects. i.e. Software Testing reduces the probability of undiscovered defects remaining in the software but even if no defects are found, it is not proof of correctness. But what if, you work extra hard, taking all precautions &amp; make your software product 99% bug-free. And the software does not meet the needs &amp; requirements of the clients. This leads us to our next principle, which states that- Absence of Error. Absence of Error - fallacy It is possible that software which is 99% bug-free is still unusable. This can be the case if the system is tested thoroughly for the wrong requirement. Software testing is not merely finding defects, but also checking that software addresses the business needs. The absence of Error is a Fallacy i.e. Finding and fixing defects does not help if the system build is unusable and does not fulfill the user's needs &amp; requirements. To solve this problem, the next principle of testing states that Early Testing Early Testing Early Testing - Testing should start as early as possible in the Software Development Life Cycle. So that any defects in the requirements or design phase are captured in the early stages. It is much cheaper to fix a Defect in the early stages of testing. But how early one should start testing? It is recommended that you start finding the bug the moment the requirements are defined. More on this principle in a later training tutorial. Testing is context-dependent Testing is context-dependent which basically means that the way you test an e-commerce site will be different from the way you test a commercial off-the-shelf application. All the developed software’s are not identical. You might use a different approach, methodologies, techniques, and types of testing depending upon the application type. For instance testing, any POS system at a retail store will be different than testing an ATM machine. <blockquote style="text-align: justify;">Useful links: <a href="https://www.youtube.com/watch?v=rFaWOw8bIMM" target="_blank" style="font-size: 16px;">7 Principles of Software Testing /video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=XDiVs2-Ggz4" target="_blank" style="font-size: 16px;">Software Testing Principles /video tutorial/rus</a> <a href="https://www.youtube.com/watch?v=YvbcTFlJMhc" target="_blank" style="font-size: 16px;">Software Testing Principles /video tutorial/rus</a> <a href="https://www.guru99.com/software-testing-seven-principles.html" target="_blank" style="font-size: 16px;">7 Principles of Software Testing /article/eng</a> <a href="https://www.softwaretestingmaterial.com/principles-of-software-testing-2/" target="_blank" style="font-size: 16px;">7 Principles of Software Testing /article/eng</a> </blockquote>

7 Principles of Software Testing - one by one.

7 Principles of Software Testing

<h3>What is SDLC?</h3> SDLC is Software Development Life Cycle. It is the sequence of activities carried out by Developers to design and develop high-quality software. Requirement collection and analysis The requirement is the first stage in the SDLC process. It is conducted by the senior team members with inputs from all the stakeholders and domain experts in the industry. Planning for the quality assurance requirements and recognization of the risks involved is also done at this stage. This stage gives a clearer picture of the scope of the entire project and the anticipated issues, opportunities, and directives which triggered the project. Requirements Gathering stage need teams to get detailed and precise requirements. This helps companies to finalize the necessary timeline to finish the work of that system. Feasibility study Once the requirement analysis phase is completed the next SDLC step is to define and document software needs. This process conducted with the help of 'Software Requirement Specification' document also known as 'SRS' document. It includes everything which should be designed and developed during the project life cycle. There are mainly five types of feasibilities checks: Economic: Can we complete the project within the budget or not? Legal: Can we handle this project as cyber law and other regulatory compliances. Operation feasibility: Can we create operations which is expected by the client? Technical: Need to check whether the current computer system can support the software Schedule: Decide that the project can be completed within the given schedule or not. Design In this third phase, the system and software design documents are prepared as per the requirement specification document. This helps define overall system architecture. This design phase serves as input for the next phase of the model. There are two kinds of design documents developed in this phase: High-Level Design (HLD) <ul><li>Brief description and name of each module</li><li>An outline about the functionality of every module</li><li>Interface relationship and dependencies between modules</li><li>Database tables identified along with their key elements</li><li>Complete architecture diagrams along with technology details </li></ul> Low-Level Design(LLD) <ul><li>Functional logic of the modules</li><li>Database tables, which include type and size</li><li>Complete detail of the interface</li><li>Addresses all types of dependency issues</li><li>Listing of error messages</li><li>Complete input and outputs for every module </li></ul> Coding Once the system design phase is over, the next phase is coding. In this phase, developers start to build the entire system by writing code using the chosen programming language. In the coding phase, tasks are divided into units or modules and assigned to the various developers. It is the longest phase of the Software Development Life Cycle process. In this phase, the Developer needs to follow certain predefined coding guidelines. They also need to use programming tools like compilers, interpreters, debuggers to generate and implement the code. Testing Once the software is complete, and it is deployed in the testing environment. The testing team starts testing the functionality of the entire system. This is done to verify that the entire application works according to the customer's requirements. During this phase, QA and testing team may find some bugs/defects which they communicate to developers. The development team fixes the bug and sends it back to QA for a re-test. This process continues until the software is bug-free, stable, and working according to the business needs of that system. Installation/Deployment Once the software testing phase is over and no bugs or errors are left in the system then the final deployment process starts. Based on the feedback given by the project manager, the final software is released and checked for deployment issues if any. Maintenance Once the system is deployed, and customers start using the developed system, the following 3 activities occur:<ul><li>Bug fixing - bugs are reported because of some scenarios which are not tested at all</li><li>Upgrade - Upgrading the application to the newer versions of the Software</li><li>Enhancement - Adding some new features into the existing software</li></ul> The main focus of this SDLC phase is to ensure that needs continue to be met and that the system continues to perform as per the specification mentioned in the first phase. <h3>Waterfall model in SDLC</h3> The waterfall is a widely accepted SDLC model. In this approach, the whole process of the software development is divided into various phases of SDLC. In this SDLC model, the outcome of one phase acts as the input for the next phase. This SDLC model is documentation-intensive, with earlier phases documenting what need be performed in the subsequent phases. <h3>V-Model in SDLC</h3> In this type of SDLC model testing and development, the phase is planned in parallel. So, there are verification phases of SDLC on one side and the validation phase on the other side. V-Model joins by Coding phase. <blockquote>Useful Links: <a href="https://www.youtube.com/watch?v=i-QyW8D3ei0" target="_blank" style="font-size: 16px;">SDLC /video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=_dr5zodeFQo" target="_blank" style="font-size: 16px;">SDLC /video tutorial/rus</a> <a href="https://www.guru99.com/software-development-life-cycle-tutorial.html" target="_blank" style="font-size: 16px;">SDLC /article/eng</a> <a href="https://habr.com/ru/company/dcmiran/blog/521718/" target="_blank" style="font-size: 16px;">SDLC /article/rus/</a></blockquote>

SDLC

<h3>What is Software Testing Life Cycle?</h3> Software Testing Life Cycle (STLC) is a sequence of specific activities conducted during the testing process to ensure software quality goals are met. STLC involves both verification and validation activities. Contrary to popular belief, Software Testing is not just a single/isolate activity, i.e. testing. It consists of a series of activities carried out methodologically to help certify your software product. STLC stands for Software Testing Life Cycle. There are following six major phases in every Software Testing Life Cycle Model (STLC Model): <ol><li style="text-align: justify;">Requirement Analysis</li><li style="text-align: justify;">Test Planning</li><li style="text-align: justify;">Test case development</li><li style="text-align: justify;">Test Environment setup</li><li style="text-align: justify;">Test Execution</li><li style="text-align: justify;">Test Cycle closure</li></ol> <h3>Requirement Collection and analysis</h3> Requirement Phase Testing also known as Requirement Analysis in which test team studies the requirements from a testing point of view to identify testable requirements and the QA team may interact with various stakeholders to understand requirements in detail. Requirements could be either functional or non-functional. Automation feasibility for the testing project is also done in this stage. Activities in Requirement Phase Testing <ul><li style="text-align: justify;">Identify types of tests to be performed. </li><li style="text-align: justify;">Gather details about testing priorities and focus.</li><li style="text-align: justify;">Prepare Requirement Traceability Matrix (RTM).</li><li style="text-align: justify;">Identify test environment details where testing is supposed to be carried out.</li><li style="text-align: justify;">Automation feasibility analysis (if required).</li></ul> Deliverables of Requirement Phase Testing <ul><li style="text-align: justify;">RTM</li></ul><ul><li style="text-align: justify;">Automation feasibility report. (if applicable)</li></ul> <h3>Test Planning</h3> Test Planning in STLC is a phase in which a Senior QA manager determines the test plan strategy along with efforts and cost estimates for the project. Moreover, the resources, test environment, test limitations and the testing schedule are also determined. The Test Plan gets prepared and finalized in the same phase. Test Planning Activities<ul><li style="text-align: justify;">Preparation of test plan/strategy document for various types of testing</li><li style="text-align: justify;">Test tool selection</li><li style="text-align: justify;">Test effort estimation</li><li style="text-align: justify;">Resource planning and determining roles and responsibilities.</li><li style="text-align: justify;">Training requirement </li></ul> Deliverables of Test Planning<ul><li style="text-align: justify;">Test plan /strategy document.</li><li style="text-align: justify;">Effort estimation document.</li></ul> <h3>Test Case Development</h3> The Test Case Development Phase involves the creation, verification and rework of test cases &amp; test scripts after the test plan is ready. Initially, the Test data is identified then created and reviewed and then reworked based on the preconditions. Then the QA team starts the development process of test cases for individual units. Test Case Development Activities<ul><li style="text-align: justify;">Create test cases, automation scripts (if applicable)</li><li style="text-align: justify;">Review and baseline test cases and scripts</li><li style="text-align: justify;">Create test data (If Test Environment is available)</li></ul> Deliverables of Test Case Development<ul><li style="text-align: justify;">Test cases/scripts</li></ul>Test data <h3>Test Environment Setup</h3> Test Environment Setup decides the software and hardware conditions under which a work product is tested. It is one of the critical aspects of the testing process and can be done in parallel with the Test Case Development Phase. Test team may not be involved in this activity if the development team provides the test environment. The test team is required to do a readiness check (smoke testing) of the given environment. Test Environment Setup Activities<ul><li style="text-align: justify;">Understand the required architecture, environment set-up and prepare hardware and software requirement list for the Test Environment.</li><li style="text-align: justify;">Setup test Environment and test data</li><li style="text-align: justify;">Perform smoke test on the build</li></ul> Deliverables of Test Environment Setup<ul><li style="text-align: justify;">Environment ready with test data set up</li><li style="text-align: justify;">Smoke Test Results.</li></ul> <h3>Test Environment Setup</h3> Test Execution Phase is carried out by the testers in which testing of the software build is done based on test plans and test cases prepared. The process consists of test script execution, test script maintenance and bug reporting. If bugs are reported then it is reverted back to development team for correction and retesting will be performed. Test Execution Activities<ul><li style="text-align: justify;">Execute tests as per plan</li><li style="text-align: justify;">Document test results, and log defects for failed cases</li><li style="text-align: justify;">Map defects to test cases in RTM</li><li style="text-align: justify;">Retest the Defect fixes</li><li style="text-align: justify;">Track the defects to closure</li></ul> Deliverables of Test Execution<ul><li style="text-align: justify;">Completed RTM with the execution status</li><li style="text-align: justify;">Test cases updated with results</li><li style="text-align: justify;">Defect reports</li></ul> <h3>Test Cycle Closure</h3> Test Cycle Closure Activities<ul><li style="text-align: justify;">Evaluate cycle completion criteria based on Time, Test coverage, Cost,Software, Critical Business Objectives, Quality</li><li style="text-align: justify;">Prepare test metrics based on the above parameters.</li><li style="text-align: justify;">Document the learning out of the project</li><li style="text-align: justify;">Prepare Test closure report</li><li style="text-align: justify;">Qualitative and quantitative reporting of quality of the work product to the customer.</li><li style="text-align: justify;">Test result analysis to find out the defect distribution by type and severity.</li></ul> Deliverables of Test Cycle Closure<ul><li style="text-align: justify;">Test Closure report</li><li style="text-align: justify;">Test metrics </li></ul> <blockquote style="text-align: justify;">Useful Links: <a href="https://www.youtube.com/watch?v=_3OhZrad8RM" target="_blank">STLC /video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=HylDB3bN6hQ" target="_blank">STLC /video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=An7HC1LolDM" target="_blank">SDLC vs STLC /video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=ZoOX8Q92zqc" target="_blank">STLC /video tutorial/rus</a> <a href="https://www.guru99.com/software-testing-life-cycle.html" target="_blank">STLC /article/eng</a> <a href="https://ru.education-wiki.com/5141467-sdlc-vs-stlc" target="_blank">SDLC vs STLC /article/rus</a></blockquote>

STLC

<h3>Verification</h3> Verification in Software Testing is a process of checking documents, design, code, and program in order to check if the software has been built according to the requirements or not. The main goal of verification process is to ensure quality of software application, design, architecture etc. The verification process involves activities like reviews, walk-throughs and inspection. <h3>Validation</h3> Validation in Software Testing is a dynamic mechanism of testing and validating if the software product actually meets the exact needs of the customer or not. The process helps to ensure that the software fulfills the desired use in an appropriate environment. The validation process involves activities like unit testing, integration testing, system testing and user acceptance testing. <h3>Verification VS Validation</h3> <table style="border-collapse: collapse; width: 98.392%; height: 172px; margin-left: 0.552764%; text-align: justify;"><tbody>
<tr>
	<td style="width: 50%;">Verification </td>
	<td style="width: 50%;">Validation</td></tr>
<tr>
	<td style="width: 50%; vertical-align: middle;">The verifying process includes checking documents, design, code, and program </td>
	<td style="width: 50%; vertical-align: middle;">It is a dynamic mechanism of testing and validating the actual product </td></tr>
<tr>
	<td style="width: 50%; vertical-align: middle;">It does not involve executing the code </td>
	<td style="width: 50%; vertical-align: middle;">It always involves executing the code </td></tr>
<tr>
	<td style="width: 50%; vertical-align: middle;">Verification uses methods like։ reviews, walkthroughs, inspections, and desk- checking etc. </td>
	<td style="width: 50%; vertical-align: middle;">It uses methods like Black Box Testing, White Box Testing, and non-functional testing </td></tr>
<tr>
	<td style="width: 50%; vertical-align: middle;">Whether the software conforms to specification is checked </td>
	<td style="width: 50%; vertical-align: middle;">It checks whether the software meets the requirements and expectations of a customer </td></tr>
<tr>
	<td style="width: 50%; vertical-align: middle;">It finds bugs early in the development cycle </td>
	<td style="width: 50%; vertical-align: middle;">It can find bugs that the verification process can not catch </td></tr>
<tr>
	<td style="width: 50%; vertical-align: middle;">Target is application and software architecture, specification, complete design, high level, and database design, etc. </td>
	<td style="width: 50%; vertical-align: middle;">Target is an actual product </td></tr>
<tr>
	<td style="width: 50%; vertical-align: middle;">QA team does verification and make sure that the software is as per the requirement in the SRS document. </td>
	<td style="width: 50%; vertical-align: middle;">With the involvement of the testing team validation is executed on software code. </td></tr>
<tr>
	<td style="width: 50%; vertical-align: middle;">It comes before validation </td>
	<td style="width: 50%; vertical-align: middle;">It comes after verification </td></tr></tbody></table> <blockquote style="text-align: justify;">Useful Links: <a href="https://www.guru99.com/verification-v-s-validation-in-a-software-testing.html" target="_blank">Validation vs Verification /article/eng</a> <a href="https://smartbear.com/blog/verification-and-validation-the-difference/" target="_blank">Difference Between Verification and Validation /article/eng</a> <a href="https://testmatick.com/ru/validatsiya-i-verifikatsiya-ponyatiya-shodstva-i-otlichiya/" target="_blank">Validation vs Verification /article/rus</a> <a href="https://www.youtube.com/watch?v=qxitgylm1EU" target="_blank">Validation vs Verification /video tutorial/eng</a></blockquote>

Differences between Verification and Validation.

Verification and Validation

<h3>Testing levels</h3> There are mainly four Levels of Testing in software testing <ul><li style="text-align: justify;">Unit Testing: checks if software components are fulfilling functionalities or not.</li><li style="text-align: justify;">Integration Testing: checks the data flow from one module to other modules.</li><li style="text-align: justify;">System Testing: evaluates both functional and non-functional needs for the testing.</li><li style="text-align: justify;">Acceptance Testing: checks the requirements of a specification or contract are met as per its delivery.</li><li style="text-align: justify;">Each of these testing levels has a specific purpose. These testing level provide value to the software development lifecycle.</li></ul> <h3>Unit testing</h3> A Unit is a smallest testable portion of system or application which can be compiled, liked, loaded, and executed. This kind of testing helps to test each module separately. The aim is to test each part of the software by separating it. It checks that component are fulfilling functionalities or not. This kind of testing is performed by developers. <blockquote style="text-align: justify; line-height: 1;">Useful Links: <a href="https://www.guru99.com/levels-of-testing.html" target="_blank">Levels of testing /article/eng</a> <a href="https://www.guru99.com/unit-testing-guide.html" target="_blank">Unit testing /article/eng</a> <a href="https://logrocon.ru/news/unit_testing" target="_blank">Unit testing /article/rus</a> <a href="https://www.youtube.com/watch?v=lj5nnGa_DIw" target="_blank">Unit testing /video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=0WtTd2fWaTE" target="_blank">Unit testing /video tutorial/arm</a></blockquote>

Levels of testing and Unit Testing overview.

Unit Testing

<h3>Integration Testing</h3> Integration means combining. For Example, in this testing phase, different software modules are combined and tested as a group to make sure that integrated system is ready for system testing. Integrating testing checks the data flow from one module to other modules. This kind of testing is performed by testers. <h3>Big-Bang Testing</h3> Big Bang Testing is an Integration testing approach in which all the components or modules are integrated together at once and then tested as a unit. This combined set of components is considered as an entity while testing. If all of the components in the unit are not completed, the integration process will not execute. Advantages:<ul><li style="text-align: justify;">Convenient for small systems.</li></ul> Disadvantages:<ul><li style="text-align: justify;">Fault Localization is difficult.</li><li style="text-align: justify;">Given the sheer number of interfaces that need to be tested in this approach, some interfaces link to be tested could be missed easily.</li><li style="text-align: justify;">Since the Integration testing can commence only after "all" the modules are designed, the testing team will have less time for execution in the testing phase.</li><li style="text-align: justify;">Since all modules are tested at once, high-risk critical modules are not isolated and tested on priority. Peripheral modules which deal with user interfaces are also not isolated and tested on priority.</li></ul> <h3>Incremental Testing</h3> In the Incremental Testing approach, testing is done by integrating two or more modules that are logically related to each other and then tested for proper functioning of the application. Then the other related modules are integrated incrementally and the process continues until all the logically related modules are integrated and tested successfully. Incremental Approach, in turn, is carried out by two different Methods:<ul><li style="text-align: justify;">Bottom Up</li><li style="text-align: justify;">Top Down</li></ul> Bottom-up Integration TestingBottom-up Integration Testing is a strategy in which the lower-level modules are tested first. These tested modules are then further used to facilitate the testing of higher-level modules. The process continues until all modules at the top level are tested. Once the lower-level modules are tested and integrated, then the next level of modules are formed. Diagrammatic Representation: <img src="https://www.tesvan.com/uploads/2021/08/bot.JPG_1628753504.JPG" alt="" width="300px"> Advantages:<ul><li style="text-align: justify;">Fault localization is easier.</li><li style="text-align: justify;">No time is wasted waiting for all modules to be developed unlike Big-bang approach</li></ul> Disadvantages:<ul><li style="text-align: justify;">Critical modules (at the top level of software architecture) which control the flow of application are tested last and may be prone to defects.</li><li style="text-align: justify;">An early prototype is not possible</li></ul> Top-down Integration TestingTop-Down Integration Testing is a method in which integration testing takes place from top to bottom following the control flow of the software system. The higher-level modules are tested first and then lower-level modules are tested and integrated in order to check the software functionality. Stubs are used for testing if some modules are not ready. Diagrammatic Representation: <img src="https://www.tesvan.com/uploads/2021/08/tgtg.JPG_1628754362.JPG" alt="" width="300px"> Advantages:<ul><li style="text-align: justify;">Fault Localization is easier.</li><li style="text-align: justify;">Possibility to obtain an early prototype.</li><li style="text-align: justify;">Critical Modules are tested on priority; major design flaws could be found and fixed first.</li></ul> Disadvantages:<ul><li style="text-align: justify;">Needs many Stubs.</li><li style="text-align: justify;">Modules at a lower level are tested inadequately</li></ul> <blockquote style="text-align: justify;">Useful Links: <a href="https://www.guru99.com/integration-testing.html" target="_blank" style="font-size: 14px;"></a><a href="https://www.guru99.com/integration-testing.html" target="_blank" style="font-size: 14px;">Integration testing /article/eng</a><a href="https://www.guru99.com/integration-testing.html" target="_blank" style="font-size: 14px;"></a> <a href="https://u-tor.com/topic/integration-testing" target="_blank" style="font-size: 14px;">Integration testing /article/eng</a> <a href="https://logrocon.ru/news/intgration_testing" target="_blank" style="font-size: 14px;">Integration testing /article/rus</a> <a href="https://www.youtube.com/watch?v=cQ39AwhjxH8" target="_blank" style="font-size: 14px;">Testing levels /video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=QYCaaNz8emY" target="_blank" style="font-size: 14px;">Integration testing /video tutorial/eng</a></blockquote>

Integration Testing

<h3>System Testing</h3> System testing is performed on a complete, integrated system. It allows checking system's compliance as per the requirements. It tests the overall interaction of components. It involves load, performance, reliability and security testing. System testing most often the final test to verify that the system meets the specification. It evaluates both functional and non-functional need for the testing. <blockquote style="text-align: justify;">Useful Links: <a href="https://www.guru99.com/system-testing.html" target="_blank">System testing /article/eng</a> <a href="https://www.xenonstack.com/insights/what-is-system-testing" target="_blank">System testing /article/eng</a> <a href="https://beqa.pro/blog/testing-levels/" target="_blank">Testing levels /article/rus</a> <a href="https://www.youtube.com/watch?v=t-1Cw2e7PYc" target="_blank">System testing /video tutorial/rus</a></blockquote>

System Testing

<h3>Acceptance Testing</h3>Acceptance testing is a test conducted to find if the requirements of a specification or contract are met as per its delivery. Acceptance testing is basically done by the user or customer. However, other stockholders can be involved in this process. <h3>Alpha Testing</h3>Alpha Testing is a type of acceptance testing; performed to identify all possible issues and bugs before releasing the final product to the end users. Alpha testing is carried out by the testers who are internal employees of the organization. The main goal is to identify the tasks that a typical user might perform and test them. To put it as simple as possible, this kind of testing is called alpha only because it is done early on, near the end of the development of the software, and before beta testing. The main focus of alpha testing is to simulate real users by using a black box and white box techniques. <h3>Beta Testing</h3>Beta Testing is performed by "real users" of the software application in "real environment" and it can be considered as a form of external User Acceptance Testing. It is the final test before shipping a product to the customers. Direct feedback from customers is a major advantage of Beta Testing. This testing helps to test products in customer's environment. Beta version of the software is released to a limited number of end-users of the product to obtain feedback on the product quality. Beta testing reduces product failure risks and provides increased quality of the product through customer validation. <blockquote style="text-align: justify;">Useful Links: <a href="https://www.guru99.com/user-acceptance-testing.html" target="_blank" style="font-size: 14px;">User acceptance testing /article/eng</a> <a href="https://www.istqb.org/certifications/acceptance-tester" target="_blank" style="font-size: 14px;">Acceptance testing /article/eng</a> <a href="https://www.calltouch.ru/blog/glossary/uat-testirovanie/" target="_blank" style="font-size: 14px;">Acceptance testing /article/rus</a> <a href="https://www.youtube.com/watch?v=JDD5EEJgpHU" target="_blank" style="font-size: 14px;">Writing acceptance tests /video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=uhkREQbRl-k" target="_blank" style="font-size: 14px;">Acceptance testing /video tutorial/rus</a> </blockquote>

Acceptance Testing as a final level of testing.

Acceptance Testing

<h3>White Box Testing</h3> White Box Testing is software testing technique in which internal structure, design and coding of software are tested to verify flow of input-output and to improve design, usability and security. In white box testing, code is visible to testers so it is also called Clear box testing, Open box testing, Transparent box testing, Code-based testing and Glass box testing. It is one of two parts of the Box Testing approach to software testing. Its counterpart, Blackbox testing, involves testing from an external or end-user type perspective. On the other hand, White box testing in software engineering is based on the inner workings of an application and revolves around internal testing. The term "WhiteBox" was used because of the see-through box concept. The clear box or WhiteBox name symbolizes the ability to see through the software's outer shell (or "box") into its inner workings. Likewise, the "black box" in "Black Box Testing" symbolizes not being able to see the inner workings of the software so that only the end-user experience can be tested. <blockquote style="text-align: justify;">Useful Links: <a href="https://www.guru99.com/white-box-testing.html" target="_blank">White-box testing article/eng</a> <a href="https://www.mend.io/resources/blog/white-box-testing/" target="_blank">White-box testing article/eng</a> <a href="https://coderlessons.com/tutorials/kachestvo-programmnogo-obespecheniia/ruchnoe-testirovanie/testirovanie-belogo-iashchika" target="_blank">White-box testing article/rus</a> <a href="https://www.youtube.com/watch?v=a-nn_lXf1uA" target="_blank">White-box testing video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=AqoMSfErDSE" target="_blank">White,Black and Gray box testing video tutorial/rus</a></blockquote>

White Box Testing

<h3>Black Box method</h3> Black Box Testing is a software testing method in which the functionalities of software applications are tested without having knowledge of internal code structure, implementation details and internal paths. Black Box Testing mainly focuses on input and output of software applications and it is entirely based on software requirements and specifications. It is also known as Behavioral Testing. <img src="https://www.tesvan.com/uploads/2021/08/black.JPG_1628843868.JPG" alt="" width="300px"> The above Black-Box can be any software system you want to test. For Example, an operating system like Windows, a website like Google, a database like Oracle or even your own custom application. Under Black Box Testing, you can test these applications by just focusing on the inputs and outputs without knowing their internal code implementation. <blockquote style="text-align: justify;">Useful Links: <a href="https://www.guru99.com/black-box-testing.html" target="_blank" style="font-size: 14px;">Black-box testing article/eng</a> <a href="https://www.imperva.com/learn/application-security/black-box-testing/" target="_blank" style="font-size: 14px;">Black-box testing article/eng</a> <a href="https://quality-lab.ru/blog/key-principles-of-black-box-testing/" target="_blank" style="font-size: 14px;">Black-box testing article/rus</a> <a href="https://www.youtube.com/watch?v=O7j3tBXO23M" target="_blank" style="font-size: 14px;">Black-box vs White-box testing video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=joTjpiohrQw" target="_blank" style="font-size: 14px;">Black-box testing video tutorial/rus</a> </blockquote>

Black Box Testing

<h3>Gray Box Testing</h3> Gray Box Testing or Gray box testing is a software testing technique to test a software product or application with partial knowledge of internal structure of the application. The purpose of grey box testing is to search and identify the defects due to improper code structure or improper use of applications. In this process, context-specific errors that are related to web systems are commonly identified. It increases the testing coverage by concentrating on all of the layers of any complex system. Gray Box Testing is a software testing method, which is a combination of both White Box Testing and Black Box Testing method. <ol><li>In White Box testing internal structure (code) is known</li><li>In Black Box testing internal structure (code) is unknown</li><li>In Grey Box Testing internal structure (code) is partially known</li></ol> <img src="https://www.tesvan.com/uploads/2021/08/gray.JPG_1628844457.JPG" alt="" width="300px"> In Software Engineering, Gray Box Testing gives the ability to test both sides of an application, presentation layer as well as the code part. It is primarily useful in Integration Testing and Penetration Testing. Example of Gray Box Testing: While testing websites feature like links or orphan links, if tester encounters any problem with these links, then he can make the changes straightaway in HTML code and can check in real time. <blockquote>Useful Links: <a href="https://www.guru99.com/grey-box-testing.html" target="_blank" style="font-size: 14px;">Gray-box testing article/eng</a> <a href="https://www.mend.io/resources/blog/gray-box-testing/" target="_blank" style="font-size: 14px;">Gray-box testing article/eng</a> <a href="https://ru.education-wiki.com/7781700-gray-box-testing" target="_blank" style="font-size: 14px;">Gray-box testing article/rus</a> <a href="https://www.youtube.com/watch?v=x-tNXvvz_KA" target="_blank" style="font-size: 14px;">Gray-box testing video tutorial/rus</a> <a href="https://www.youtube.com/watch?v=VD5tOODUOzs" target="_blank" style="font-size: 14px;">Gray-box testing video tutorial/eng</a> </blockquote>

Gray Box Testing

<h3>Visual (GUI) Testing</h3> GUI Testing is a software testing type that checks the Graphical User Interface of the Software. The purpose of Graphical User Interface (GUI) Testing is to ensure the functionalities of software application work as per specifications by checking screens and controls like menus, buttons, icons, etc. GUI is what the user sees. Say if you visit guru99.com what you will see say homepage it is the GUI (graphical user interface) of the site. A user does not see the source code. The interface is visible to the user. Especially the focus is on the design structure, images that they are working properly or not. <blockquote style="text-align: justify;">Useful Links: <a href="https://www.guru99.com/gui-testing.html" target="_blank" style="font-size: 14px;">GUI testing article/eng</a> <a href="https://www.browserstack.com/guide/visual-testing-beginners-guide" target="_blank" style="font-size: 14px;">Visual testing article/eng</a> <a href="https://www.youtube.com/watch?v=crbwyGlcXm0" target="_blank" style="font-size: 14px;">Visual testing video tutorial/rus</a> </blockquote>

Visual or GUI Testing as a testing method.

Visual Testing

<h3>Ad Hoc Testing</h3> Ad hoc Testing is an informal or unstructured software testing type that aims to break the testing process in order to find possible defects or errors at an early possible stage. Ad hoc testing is done randomly and it is usually an unplanned activity which does not follow any documentation and test design techniques to create test cases. Ad hoc Testing does not follow any structured way of testing and it is randomly done on any part of application. Main aim of this testing is to find defects by random checking. Ad Hoc testing can be achieved with the Software testing technique called Error Guessing. Error guessing can be done by the people having enough experience on the system to "guess" the most likely source of errors. This testing requires no documentation/ planning /process to be followed. Since this testing aims at finding defects through random approach, without any documentation, defects will not be mapped to test cases. This means that, sometimes, it is very difficult to reproduce the defects as there are no test steps or requirements mapped to it. <blockquote style="text-align: justify;">Useful Links: <a href="https://www.guru99.com/adhoc-testing.html" target="_blank" style="font-size: 14px;">Ad-hoc testing article/eng</a> <a href="https://coderlessons.com/tutorials/kachestvo-programmnogo-obespecheniia/ruchnoe-testirovanie/spetsialnoe-testirovanie" target="_blank" style="font-size: 14px;">Ad-hoc testing article/rus</a> <a href="https://www.youtube.com/watch?v=Nk_bC9WmuC4" target="_blank" style="font-size: 14px;">Ad-hoc testing video tutorial/eng</a> </blockquote>

Ad Hoc Testing

<h3>Manual Testing Method</h3> <ol><li style="text-align: justify;">Manual Testing is a type of Software Testing where Testers manually execute test cases without using any automation tools. Manual Testing is the most primitive of all testing types and helps find bugs in the software system.</li><li style="text-align: justify;">Any new application must be manually tested before its testing can be automated. Manual Testing requires more effort but is necessary to check automation feasibility.</li><li style="text-align: justify;">Manual Testing does not require knowledge of any testing tool.</li></ol> <h3 style="text-align: justify;">Goals of Manual Testing</h3> <ol><li style="text-align: justify;">The key concept of manual testing is to ensure that the application is error free and it is working in conformance to the specified functional requirements.</li><li style="text-align: justify;">Test Suites or cases, are designed during the testing phase and should have 100% test coverage.</li><li style="text-align: justify;">It also makes sure that reported defects are fixed by developers and re-testing has been performed by testers on the fixed defects.</li><li style="text-align: justify;">Basically, this testing checks the quality of the system and delivers bug-free product to the customer.</li></ol> <blockquote style="text-align: justify;">Useful Links: <a href="https://www.guru99.com/manual-testing.html" target="_blank" style="font-size: 14px;">Manual testing article/eng</a> <a href="https://www.softwaretestinghelp.com/manual-testing-tutorial-1/" target="_blank" style="font-size: 14px;">Manual testing article/eng</a> <a href="https://www.youtube.com/watch?v=AjkYTJklAa8" target="_blank" style="font-size: 14px;">Manual testing video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=1lHCM2Br2eA" target="_blank" style="font-size: 14px;">Manual testing video tutorial/ru</a> </blockquote>

Manual Testing

<h3>Automated Testing Method</h3> Automated testing is the application of software tools to automate a human-driven manual process of reviewing and validating a software product. Most modern software projects now include automated testing from inception. <h3>Selenium Locators</h3> Locator is a command that tells Selenium IDE which GUI elements (say Text Box, Buttons, Check Boxes etc) its needs to operate on. Identification of correct GUI elements is a prerequisite to creating an automation script. But accurate identification of GUI elements is more difficult than it sounds. The choice of locator depends largely on your Application Under Test. In this tutorial, we will toggle between Facebook, new tours.demoaut on the basis of locators that these applications support. Likewise in your Testing project, you will select any of the above-listed element locators in Selenium webdriver, based on your application support. Locating by ID This is the most common way of locating elements since ID's are supposed to be unique for each element. Target Format: id=id of the element Locating by Name Locating elements by name are very similar to locating by ID, except that we use the "name=" prefix instead. Target Format: name=name of the element Locating by Name using Filters Filters can be used when multiple elements have the same name. Filters are additional attributes used to distinguish elements with the same name. Target Format: name=name_of_the_element filter=value_of_filte Locating by Link Text This type of CSS locator in Selenium applies only to hyperlink texts. We access the link by prefixing our target with "link=" and then followed by the hyperlink text. Target Format: link=link_text Locating by CSS Selector CSS Selectors in Selenium are string patterns used to identify an element based on a combination of HTML tag, id, class, and attributes. Locating by CSS Selectors in Selenium is more complicated than the previous methods, but it is the most common locating strategy of advanced Selenium users because it can access even those elements that have no ID or name. CSS Selectors in Selenium have many formats, but we will only focus on the most common ones.<ul><li style="text-align: justify;">Tag and ID</li><li style="text-align: justify;">Tag and class</li><li style="text-align: justify;">Tag and attribute</li><li style="text-align: justify;">Tag, class, and attribute</li><li style="text-align: justify;">Inner text</li></ul> When using this strategy, we always prefix the Target box with "css=" as will be shown in the following examples. Locating by CSS Selector - Tag and IDAgain, we will use Facebook's Email text box in this example. As you can remember, it has an ID of "email," and we have already accessed it in the "Locating by ID" section. This time, we will use a Selenium CSS Selector with ID in accessing that very same element. Locating by CSS Selector - Tag and Class Locating by CSS Selector in Selenium using an HTML tag and a class name is similar to using a tag and ID, but in this case, a dot (.) is used instead of a hash sign. Locating by CSS Selector - Tag and Attribute This strategy uses the HTML tag and a specific attribute of the element to be accessed. Locating by CSS Selector - tag, class, and attribute Locating by CSS Selector - inner textAs you may have noticed, HTML labels are seldom given id, name, or class attributes. So, how do we access them? The answer is through the use of their inner texts. Inner texts are the actual string patterns that the HTML label shows on the page. <h3>API Testing</h3> API (Application Programming Interface) is a computing interface which enables communication and data exchange between two separate software systems. Software system that executes an API includes several functions/subroutines that another software system can perform. API defines requests that can be made, how to make requests, data formats that can be used, etc. between two software systems. API testing is a software testing type that validates Application Programming Interfaces (APIs). The purpose of API Testing is to check the functionality, reliability, performance, and security of the programming interfaces. In API Testing, instead of using standard user inputs(keyboard) and outputs, you use software to send calls to the API, get output, and note down the system's response. API tests are very different from GUI Tests and won't concentrate on the look and feel of an application. It mainly concentrates on the business logic layer of the software architecture. API automation Testing requires an application that can be interacted via an API. In order to test an API, you will need to<ul><li style="text-align: justify;">Use Testing Tool to drive the API</li><li style="text-align: justify;">Write your own code to test the API</li></ul> Test Cases for API TestingTest cases of API testing are based on։ <ul><li style="text-align: justify;">Return value based on input condition: it is relatively easy to test, as input can be defined and results can be authenticated</li><li style="text-align: justify;">Does not return anything: When there is no return value, a behavior of API on the system to be checked</li><li style="text-align: justify;">Trigger some other API/event/interrupt: If an output of an API triggers some event or interrupt, then those events and interrupt listeners should be tracked</li><li style="text-align: justify;">Update data structure: Updating data structure will have some outcome or effect on the system, and that should be authenticated</li><li style="text-align: justify;">Modify certain resources: If API call modifies some resources, then it should be validated by accessing respective resources</li></ul> <h3>Docker</h3> Docker is a software development platform for virtualization with multiple Operating systems running on the same host. It helps to separate infrastructure and applications in order to deliver software quickly. Unlike Hypervisors, which are used for creating VM (Virtual machines), virtualization in Docker is performed on system-level, also called Docker containers. As you can see the difference in the image below, Docker containers run on top of the host's Operation system. This helps you to improves efficiency and security. Moreover, we can run more containers on the same infrastructure than we can run Virtual machines because containers use fewer resources. Why use Docker?<ul><li style="text-align: justify;">Docker is computer software used for Virtualization in order to have multiple Operating systems running on the same host</li><li style="text-align: justify;">Docker is the client-server type of application which means we have clients who relay to the server</li><li style="text-align: justify;">Docker images are the "source code" for our containers; we use them to build</li><li style="text-align: justify;">Dockerfile has two types of registries 1.) public and 2)private registries</li><li style="text-align: justify;">Containers are the organizational units of Docker volume. In simple terms, an image is a template, and a container is a copy of that template. You can have multiple containers (copies) of the same image.</li></ul> Docker ArchitectureNow in this Docker container tutorial, let's talk about Docker main components in the Docker Architecture: <img src="https://www.tesvan.com/uploads/2021/08/docker.JPG_1629100789.JPG" alt="" width="300px"> Docker Engine Docker is the client-server type of application which means we have clients who relay to the server. So the Docker daemon called: dockerd is the Docker engine which represents the server. The docker daemon and the clients can be run on the same or remote host, and they communicate through command line client binary, as well as a full RESTful API to interact with the daemon: dockerd. Docker Images Docker images are the "source code" for our containers; we use them to build containers. They can have software pre-installed which speeds up deployment. They are portable, and we can use existing images or build our own. Docker Registries Docker stores the images we build in registries. There are public and private registries. Docker company has public registry called Docker hub, where you can also store images privately. Docker hub has millions of images, which you can start using now. Docker Containers Containers are the organizational units and one of the Docker basics concept. When we build an image and start running it; we are running in a container. The container analogy is used because of the portability of the software we have running in our container. We can move it, in other words, "ship" the software, modify, manage, create or get rid of it, destroy it, just as cargo ships can do with real containers. In simple terms, an image is a template, and a container is a copy of that template. You can have multiple containers (copies) of the same image. <h3>Jenkins</h3> Jenkins is an open-source Continuous Integration server written in Java for orchestrating a chain of actions to achieve the Continuous Integration process in an automated fashion. Jenkins supports the complete development life cycle of software from building, testing, documenting the software, deploying, and other stages of the software development life cycle. Jenkins is a widely used application around the world that has around 300k installations and growing day by day. By using Jenkins, software companies can accelerate their software development process, as Jenkins can automate build and test at a rapid rate. It is a server-based application and requires a web server like Apache Tomcat. The reason Jenkins software became so popular is that of its monitoring of repeated tasks which arise during the development of a project. For example, if your team is developing a project, Jenkins will continuously test your project builds and show you the errors in early stages of your development. What is Continuous Integration? Continuous Integration is a process of integrating code changes from multiple developers in a single project many times. The software is tested immediately after a code commit. With each code commit, code is built and tested. If the test is passed, the build is tested for deployment. If the deployment is successful, the code is pushed to production. This commit, build, test, and deploy is a continuous process and hence the name continuous integration/deployment. How does Jenkins work? Jenkins is a server-based application and requires a web server like Apache Tomcat to run on various platforms like Windows, Linux, macOS, Unix, etc. To use Jenkins, you need to create pipelines which are a series of steps that a Jenkins server will take. Jenkins Continuous Integration Pipeline is a powerful instrument that consists of a set of tools designed to host, monitor, compile and test code, or code changes, like: <ul><li style="text-align: justify;">Continuous Integration Server (Jenkins, Bamboo, CruiseControl, TeamCity, and others)</li><li style="text-align: justify;">Source Control Tool (e.g., CVS, SVN, GIT, Mercurial, Perforce, ClearCase and others)</li><li style="text-align: justify;">Build tool (Make, ANT, Maven, Ivy, Gradle, and others)</li><li style="text-align: justify;">Automation testing framework (Selenium, Appium, TestComplete, UFT, and others)</li></ul> Jenkin History<ul><li style="text-align: justify;">Kohsuke Kawaguchi, a Java developer, working at SUN Microsystems, was tired of building the code and fixing errors repetitively. In 2004, created an automation server called Hudson that automates build and test task.</li><li style="text-align: justify;">In 2011, Oracle who owned Sun Microsystems had a dispute with Hudson open source community, so they forked Hudson and renamed it as Jenkins.</li><li style="text-align: justify;">Both Hudson and Jenkins continued to operate independently. But in short span of time, Jenkins acquired a lot of projects and contributors while Hudson remained with only 32 projects. With time, Jenkins became more popular, and Hudson is not maintained anymore.</li></ul> <blockquote style="text-align: justify;">Useful Links: <a href="https://www.guru99.com/automation-testing.html" target="_blank" style="font-size: 14px;">Automation testing article/eng</a> <a href="https://www.guru99.com/introduction-to-selenium.html" target="_blank" style="font-size: 14px;">Selenium as an automation testing tool article/eng</a> <a href="https://www.guru99.com/locators-in-selenium-ide.html" target="_blank" style="font-size: 14px;">Selenium locators article/eng</a> <a href="https://www.ibm.com/cloud/learn/docker" target="_blank" style="font-size: 14px;">Docker article/eng</a> <a href="https://www.guru99.com/api-testing.html" target="_blank" style="font-size: 14px;">API testing article/eng</a> <a href="https://www.guru99.com/jenkin-continuous-integration.html" target="_blank" style="font-size: 14px;">Jenkins article/eng</a> <a href="https://www.youtube.com/watch?v=QtZ4yV49RtA" target="_blank" style="font-size: 14px;">Automation testing video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=TH4qot56Uqg" target="_blank" style="font-size: 14px;">Automation testing video tutorial/arm</a> <a href="https://www.youtube.com/watch?v=TNImFcYqb40" target="_blank" style="font-size: 14px;">Automation testing video tutorial/rus</a> <a href="https://www.youtube.com/watch?v=jK_4nnEJVHQ" target="_blank" style="font-size: 14px;">Locators in Selenuim video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=9-iVt0MIqNY" target="_blank" style="font-size: 14px;">Xpath in Selenium video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=89yWXXIOisk" target="_blank" style="font-size: 14px;">Jenkins video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=wi-MGFhrad0&amp;list=PLhW3qG5bs-L99pQsZ74f-LC-tOEsBp2rK" target="_blank" style="font-size: 14px;">Docker video tutorial/eng</a> </blockquote>

Automated Testing

<h3>Manual Testing VS Automation Testing</h3> <table style="border-collapse: collapse; width: 98.9782%; height: 273px;"><tbody>
<tr>
	<td style="width: 50%; text-align: center;">Manual Testing </td>
	<td style="width: 50%; text-align: center;">Automated Testing </td></tr>
<tr>
	<td style="width: 50%;">Manual testing requires human intervention for test execution. </td>
	<td style="width: 50%;">Automation Testing is the use of tools to execute test cases․ </td></tr>
<tr>
	<td style="width: 50%;">Manual testing will require skilled labour, long time &amp; will imply high costs. </td>
	<td style="width: 50%;">Automation Testing saves time, cost, and manpower. Once recorded, it's easier to run an automated test suite․ </td></tr>
<tr>
	<td style="width: 50%;">Any type of application can be tested manually, certain testing types like ad-hoc and monkey testing are more suited for manual execution. </td>
	<td style="width: 50%;">Automated testing is recommended only for stable systems and is mostly used for Regression Testing․ </td></tr>
<tr>
	<td style="width: 50%;">Manual testing can become repetitive and boring. </td>
	<td style="width: 50%;">The boring part of executing same test cases time and again is handled by automation software in Automation Testing. </td></tr></tbody></table> <blockquote>Useful Links: <a href="https://www.guru99.com/difference-automated-vs-manual-testing.html" target="_blank" style="font-size: 14px;">Manual testing vs Automation testing article/eng</a> <a href="https://auriga.ru/" target="_blank" style="font-size: 14px;">Manual testing vs Automation testing article/rus</a> <a href="https://www.youtube.com/watch?v=SEzPFlnI7mY" target="_blank" style="font-size: 14px;">Manual testing vs Automation testing video tutorial/eng</a> </blockquote>

Difference between Manual testing and Automation testing.

Manual Testing VS Automation Testing

<h3>Functional Testing</h3> What does Functional Testing check? Functional Testing is a type of software testing that validates the software system against the functional requirements/specifications. The purpose of Functional tests is to test each function of the software application, by providing appropriate input, verifying the output against the Functional requirements. Functional testing mainly involves black box testing and it is not concerned about the source code of the application. This testing checks User Interface, APIs, Database, Security, Client/Server communication and other functionality of the Application Under Test. The testing can be done either manually or using automation. Functional Testing Steps Following is a step by step process on How to do Functional Testing: <ul><li style="text-align: justify;">Understand the Functional Requirements</li><li style="text-align: justify;">Identify test input or test data based on requirements</li><li style="text-align: justify;">Compute the expected outcomes with selected test input values</li><li style="text-align: justify;">Execute test cases</li><li style="text-align: justify;">Compare actual and computed expected results</li></ul> <blockquote style="text-align: justify;">Useful Links: <a href="https://www.guru99.com/functional-testing.html" target="_blank" style="font-size: 14px;">Functional testing article/eng</a> <a href="https://www.applause.com/blog/functional-testing-types-examples" target="_blank" style="font-size: 14px;">Functional testing types article/eng</a> <a href="https://coderlessons.com/tutorials/kachestvo-programmnogo-obespecheniia/ruchnoe-testirovanie/funktsionalnoe-testirovanie-2" target="_blank" style="font-size: 14px;">Functional testing article/rus</a> <a href="https://www.youtube.com/watch?v=IGnZHgjU42Y" target="_blank" style="font-size: 14px;">Functional testing video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=B1-1BqAr1f4" target="_blank" style="font-size: 14px;">Functional testing video tutorial/rus</a> </blockquote>

Functional Testing

<h3>Non Functional Testing</h3> Non-Functional Testing is defined as a type of Software testing to check non-functional aspects (performance, usability, reliability, etc) of a software application. It is designed to test the readiness of a system as per nonfunctional parameters which are never addressed by functional testing. An excellent example of non-functional test would be to check how many people can simultaneously login into a software. <h3>Usability Testing</h3> <ul><li style="text-align: justify;">Usability testing is a technique used in user-centered interaction design to evaluate a product by testing it on users.</li><li style="text-align: justify;">This can be seen as an irreplaceable usability practice, since it gives direct input on how real users use the system.</li><li style="text-align: justify;">Usability testing generally involves measuring how well test subjects respond in four areas: efficiency, accuracy, recall, and emotional response. </li></ul> <h3>Recovery Testing</h3> <ul><li style="text-align: justify;">Recovery testing is the activity of testing how well an application is able to recover from crashes, hardware failures and other similar problems.</li><li style="text-align: justify;">E.g. While an application is receiving data from a network, unplug the connecting cable. After some time, plug the cable back in and analyze the application's ability to continue receiving data from the point at which the network connection disappeared.</li></ul> <h3>Compatibility Testing</h3> <ul><li style="text-align: justify;">Compatibility testing, part of software non-functional tests, is testing conducted on the application to evaluate the application's compatibility with the computing environment.</li><li style="text-align: justify;">Computing environment may contain different OS types (IOS 6, IOS 7), different types of browsers (Chrome, Firefox, IE).</li></ul> <h3>Performance Testing</h3> <ul><li style="text-align: justify;">Performance testing is generally executed to determine how a system or sub - system performs in terms of responsiveness and stability under a particular workload.</li><li style="text-align: justify;">It can also serve to investigate measure, validate or verify other quality attributes of the system, such as scalability, reliability and resource usage.</li></ul> <h3>Performance Testing Metrics</h3> The basic parameters monitored during performance testing include:<ul><li style="text-align: justify;">Processor Usage - an amount of time processor spends executing non-idle threads.</li><li style="text-align: justify;">Memory use - amount of physical memory available to processes on a computer.</li><li style="text-align: justify;">Disk time - amount of time disk is busy executing a read or write request.</li><li style="text-align: justify;">Bandwidth - shows the bits per second used by a network interface.</li><li style="text-align: justify;">Private bytes - number of bytes a process has allocated that can't be shared amongst other processes. These are used to measure memory leaks and usage.</li><li style="text-align: justify;">Committed memory - amount of virtual memory used.</li><li style="text-align: justify;">Memory pages/second - number of pages written to or read from the disk in order to resolve hard page faults. Hard page faults are when code not from the current working set is called up from elsewhere and retrieved from a disk.</li><li style="text-align: justify;">Page faults/second - the overall rate in which fault pages are processed by the processor. This again occurs when a process requires code from outside its working set.</li><li style="text-align: justify;">CPU interrupts per second - is the avg. number of hardware interrupts a processor is receiving and processing each second.</li><li style="text-align: justify;">Disk queue length - is the avg. no. of read and write requests queued for the selected disk during a sample interval.</li><li style="text-align: justify;">Network output queue length - length of the output packet queue in packets. Anything more than two means a delay and bottlenecking needs to be stopped.</li><li style="text-align: justify;">Network bytes total per second - rate which bytes are sent and received on the interface including framing characters.</li><li style="text-align: justify;">Response time - time from when a user enters a request until the first character of the response is received.</li><li style="text-align: justify;">Throughput - rate a computer or network receives requests per second.</li><li style="text-align: justify;">Amount of connection pooling - the number of user requests that are met by pooled connections. The more requests met by connections in the pool, the better the performance will be.</li><li style="text-align: justify;">Maximum active sessions - the maximum number of sessions that can be active at once.</li><li style="text-align: justify;">Hit ratios - This has to do with the number of SQL statements that are handled by cached data instead of expensive I/O operations. This is a good place to start for solving bottlenecking issues.</li><li style="text-align: justify;">Hits per second - the no. of hits on a web server during each second of a load test.</li><li style="text-align: justify;">Rollback segment - the amount of data that can rollback at any point in time.</li><li style="text-align: justify;">Database locks - locking of tables and databases needs to be monitored and carefully tuned.</li><li style="text-align: justify;">Top waits - are monitored to determine what wait times can be cut down when dealing with the how fast data is retrieved from memory</li><li style="text-align: justify;">Thread counts - An applications health can be measured by the no. of threads that are running and currently active.</li><li style="text-align: justify;">Garbage collection - It has to do with returning unused memory back to the system. Garbage collection needs to be monitored for efficiency</li></ul> <h3>Performance Testing Types</h3> <ol><li style="text-align: justify;">Load testing - checks the application's ability to perform under anticipated user loads. The objective is to identify performance bottlenecks before the software application goes live.</li><li style="text-align: justify;">Stress testing - involves testing an application under extreme workloads to see how it handles high traffic or data processing. The objective is to identify the breaking point of an application.</li><li style="text-align: justify;">Volume testing - Under Volume Testing large no. of. Data is populated in a database and the overall software system's behavior is monitored. The objective is to check software application's performance under varying database volumes.</li><li style="text-align: justify;">Scalability testing - The objective of scalability testing is to determine the software application's effectiveness in "scaling up" to support an increase in user load. It helps plan capacity addition to your software system.</li><li style="text-align: justify;">Endurance testing - is done to make sure the software can handle the expected load over a long period of time.</li></ol> <h3>Security Testing</h3> <ol><li style="text-align: justify;">Security testing is a process to determine that an information system protects data and maintains functionality as intended.</li><li style="text-align: justify;">The six basic security concepts that need to be covered by security testing are:</li></ol> <ul><li style="text-align: justify;">Confidentiality</li><li style="text-align: justify;">Integrity</li><li style="text-align: justify;">Authentication</li><li style="text-align: justify;">Availability</li><li style="text-align: justify;">Authorizationnon-repudiation.</li><li style="text-align: justify;">Availability Testing</li></ul> <h3>Internationalization and Localization Testing</h3> <ul><li style="text-align: justify;">Internationalization and localization are means of adapting computer applications to different languages, regional differences and technical requirements of a target market.</li><li style="text-align: justify;">Internationalization is the process of designing a software application so that it can be adapted to various languages and regions without engineering changes.</li><li style="text-align: justify;">Localization is the process of adapting internationalized software for a specific region or language by adding locale-specific components and translating text.</li></ul> <blockquote style="text-align: justify;">Useful Links: <a href="https://www.guru99.com/non-functional-testing.html" target="_blank" style="font-size: 14px;">Non-functionl testing article/eng</a> <a href="https://diffy.website/blog/functional-vs-non-functional-testing" target="_blank" style="font-size: 14px;">Functional testing vs Non-functional testing article/eng</a> <a href="https://coderlessons.com/tutorials/kachestvo-programmnogo-obespecheniia/ruchnoe-testirovanie/ne-funktsionalnoe-testirovanie" target="_blank" style="font-size: 14px;">Non-functional testing article/rus</a> <a href="https://www.youtube.com/watch?v=j_79AXkG4PY" target="_blank" style="font-size: 14px;">Functional testing vs Non-functional testing video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=0BszE2j8Zug" target="_blank" style="font-size: 14px;">Functional testing vs Non-functional testing video tutorial/rus</a> </blockquote>

Non Functional Testing

<h3>Maintenance Testing</h3> Maintenance Testing is done on the already deployed software. The deployed software needs to be enhanced, changed or migrated to other hardware. The Testing done during this enhancement, change and migration cycle is known as maintenance testing. <blockquote style="text-align: justify;">Useful Links: <a href="https://www.softwaretestingmaterial.com/maintenance-testing/" target="_blank" style="font-size: 14px;">Maintenance testing article/eng</a> <a href="https://www.youtube.com/watch?v=7B69Z35BvD4" target="_blank" style="font-size: 14px;">Maintenance testing video tutorial/eng</a> </blockquote>

Maintenance Testing

<h3>What is Defect?</h3> The variation between the actual results and expected results is known as defect. If a developer finds an issue and corrects it by himself in the development phase then it’s called a defect. <h3>What is Bug?</h3> If testers find any mismatch in the application/system in testing phase then they call it as Bug. As I mentioned earlier, there is a contradiction in the usage of Bug and Defect. People widely say the bug is an informal name for the defect. <h3>What is Error?</h3> We can’t compile or run a program due to coding mistake in a program. If a developer unable to successfully compile or run a program then they call it as an error. <h3>What is Failure?</h3> Once the product is deployed and customers find any issues then they call the product as a failure product. After release, if an end user finds an issue then that particular issue is called as failure. <blockquote style="text-align: justify;">Useful Links: <a href="https://www.360logica.com/blog/difference-between-defect-error-bug-failure-and-fault/" target="_blank">Difference between Defect, Error,Bug, and Failure article/eng</a> <a href="https://www.youtube.com/watch?v=53braDId-RQ" target="_blank">Defect, Error,Bug, and Failure video tutorial/eng</a></blockquote>

What is the difference between Defect, Error, Bug, Failure?

Defect, Error, Bug, Failure

<h3>Bug Life Cycle</h3> Bug/Defect Life Cycle or Bug Life Cycle in software testing is the specific set of states that defect or bug goes through in its entire life. The purpose of Defect life cycle is to easily coordinate and communicate current status of defect which changes to various assignees and make the defect fixing process systematic and efficient. Defect Status Defect Status or Bug Status in defect life cycle is the present state from which the defect or a bug is currently undergoing. The goal of defect status is to precisely convey the current state or progress of a defect or bug in order to better track and understand the actual progress of the defect life cycle. The number of states that a defect goes through varies from project to project. Below lifecycle diagram, covers all possible states: <ol><li style="text-align: justify;">New: When a new defect is logged and posted for the first time. It is assigned a status as NEW.</li><li style="text-align: justify;">Assigned: Once the bug is posted by the tester, the lead of the tester approves the bug and assigns the bug to the developer team</li><li style="text-align: justify;">Open: The developer starts analyzing and works on the defect fix</li><li style="text-align: justify;">Fixed: When a developer makes a necessary code change and verifies the change, he or she can make bug status as "Fixed."</li><li style="text-align: justify;">Pending retest: Once the defect is fixed the developer gives a particular code for retesting the code to the tester. Since the software testing remains pending from the testers end, the status assigned is "pending retest."</li><li style="text-align: justify;">Retest: Tester does the retesting of the code at this stage to check whether the defect is fixed by the developer or not and changes the status to "Re-test."</li><li style="text-align: justify;">Verified: The tester re-tests the bug after it got fixed by the developer. If there is no bug detected in the software, then the bug is fixed and the status assigned is "verified."</li><li style="text-align: justify;">Reopen: If the bug persists even after the developer has fixed the bug, the tester changes the status to "reopened". Once again the bug goes through the life cycle.</li><li style="text-align: justify;">Closed: If the bug is no longer exists then tester assigns the status "Closed."</li><li style="text-align: justify;">Duplicate: If the defect is repeated twice or the defect corresponds to the same concept of the bug, the status is changed to "duplicate."</li><li style="text-align: justify;">Rejected: If the developer feels the defect is not a genuine defect then it changes the defect to "rejected."</li><li style="text-align: justify;">Deferred: If the present bug is not of a prime priority and if it is expected to get fixed in the next release, then status "Deferred" is assigned to such bugs</li><li style="text-align: justify;">Not a bug:If it does not affect the functionality of the application then the status assigned to a bug is "Not a bug"</li></ol> <img src="https://www.tesvan.com/uploads/2021/08/bug2.jpg_1629213510.jpg" alt="" width="300px"> <ol><li style="text-align: justify;">Tester finds the defect</li><li style="text-align: justify;">Status assigned to defect- New</li><li style="text-align: justify;">A defect is forwarded to Project Manager for analyze</li><li style="text-align: justify;">Project Manager decides whether a defect is valid</li><li style="text-align: justify;">Here the defect is not valid- a status is given "Rejected."</li><li style="text-align: justify;">So, project manager assigns a status rejected. If the defect is not rejected then the next step is to check whether it is in scope. Suppose we have another function- email functionality for the same application, and you find a problem with that. But it is not a part of the current release when such defects are</li><li style="text-align: justify;">assigned as a postponed or deferred status.</li><li style="text-align: justify;">Next, the manager verifies whether a similar defect was raised earlier. If yes defect is assigned a status duplicate.</li><li style="text-align: justify;">If no the defect is assigned to the developer who starts fixing the code. During this stage, the defect is assigned a status in- progress.</li><li style="text-align: justify;">Once the code is fixed. A defect is assigned a status fixed</li><li style="text-align: justify;">Next, the tester will re-test the code. In case, the Test Case passes the defect is closed. If the test cases fail again, the defect is re-opened and assigned to the developer.</li><li style="text-align: justify;">Consider a situation where during the 1st release of Flight Reservation a defect was found in Fax order that was fixed and assigned a status closed. During the second upgrade release the same defect again re-surfaced. In such cases, a closed defect will be re-opened.</li></ol> <blockquote style="text-align: justify;">Useful Links: <a href="https://www.guru99.com/defect-life-cycle.html" target="_blank" style="font-size: 14px;">Defect/Bug life cycle article/eng</a> <a href="https://www.youtube.com/watch?v=EZGDyFPHFMw" target="_blank" style="font-size: 14px;">Bug life cycle video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=ndwA0ywELvg" target="_blank" style="font-size: 14px;">Bug life cycle video tutorial/rus</a> </blockquote>

Bug Life Cycle

<h3>Defect Severity</h3> Every defect impacts on the system at some level. This impact is measured by the “Severity” parameter. Severity type is categorized by Software Tester based on the Test Case and functional / requirement understanding. It also indicates the seriousness of the issue occurring on the application. Each Defect management tool categories Severity in different way. <h3 style="text-align: justify;">Severity Levels</h3> A defect that completely crashes the system and Tester is no longer able to move further with the testing. In another scenario when whole feature / functionality is missing from the application, this can be considered as a Blocker defect. Almost all the time Blocker severity defects are having highest priority. Critical Severity: A highly severe defect causing the system failure or functionality collapse. But user is able to access some of it’s functions or the same scenario is executable some other way. Almost all the time Critical severity defects are having highest priority. Major Severity: Defect falling under Major severity is generally functionality specific defects. It does not cause any system failure kind of situation. But such defects are equally important and they should be resolved without any unnecessary delay. Minor &amp; Trivial Severity: Defects having small UI issues, spelling mistakes in content, minor alignment issues, color shades are reported as minor or trivial defects. These issues do not affect any of the functionality and keeping they open long time won’t make any difference. <h3>Defect Priority</h3> Priority is defined to set the order in which the reported defects should be resolved. Usually Priority is set by Software Tester or QA Lead and developers focus on higher priority defects first following the descending order. Priority can be categorized in three layers. <h3 style="text-align: justify;">Priority levels</h3> High Priority (P1): Defects falling under P1 category must be resolved and closed as soon as possible. Due to such defects testing of entire application is blocked and Tester can not move any further. Medium Priority (P2): Once all the defects with High priority are resolved, next focus should be on Medium level defects. Normally functional defects such as a feature is not working as it is supposed to be, major cosmetics errors, validation errors are considered as Medium priority defects. Such issues don’t stop you to perform further testing. Low Priority (P3): These defects are taken into consideration once all High &amp; Major priority defects are resolved. Minor UI issues, spelling mistakes, alignment issues, color code mistakes should be considered as Low priority defects. In short, by providing Priority to a Defect we set the order in which all the reported defects to be resolved. <h3 style="text-align: justify;">Examples</h3> SCENARIO 1: HIGH PRIORITY &amp; BLOCKER SEVERITY <ul><li style="text-align: justify;">A very common example, User is not able to Login into application with proper credentials. This is a very critical scenario which needs to be fixed as soon as possible.</li><li style="text-align: justify;">In an E-Commerce website User is not able to add the produce into the Cart / not able to check-out for payment from the cart. If occurred on the live application, this issue can impact on the business at great level.</li><li style="text-align: justify;">After registration, User is not getting the Link to complete the registration process.</li><li style="text-align: justify;">System is crashed when providing invalid keywords (e.g: XSS scripts) in the Search box.</li></ul> SCENARIO 2: LOW PRIORITY &amp; LOW SEVERITY <ul><li style="text-align: justify;"> Minor spelling mistakes on the pages like “Site Map”, “Career” or “Company Blog” pages.</li><li style="text-align: justify;">Color of the button on About Us page is slightly different.</li><li style="text-align: justify;">Minor alignment issues in the content of the Company Blogs page.</li></ul> SCENARIO 3: HIGH PRIORITY &amp; LOW SEVERITY <ul><li style="text-align: justify;">A very common example, “Company Logo” is not displayed as expected. This defect is not affecting any functional scenarios but it can impact on the company’s brand value. So, this issue should be fixed without any delay.</li></ul> <blockquote style="text-align: justify;">Useful Links: <a href="https://www.guru99.com/defect-severity-in-software-testing.html" target="_blank" style="font-size: 14px;">Defect severity and priority article/eng</a> <a href="https://www.performance-lab.ru/blog/sereznost" target="_blank" style="font-size: 14px;">Defect severity and priority article/rus</a> <a href="https://www.youtube.com/watch?v=HW_tnUnUav8" target="_blank" style="font-size: 14px;">Defect severity and priority video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=ZyiV9fmUzjk" target="_blank" style="font-size: 14px;">Defect severity and priority video tutorial/rus</a> </blockquote>

How to define the Priority and Severity of the bug?

Defect Severity and Priority

<h3>Defect Report</h3> is a document that identifies and describes a defect detected by a tester. The purpose of a defect report is to state the problem as clearly as possible so that developers can replicate the defect easily and fix it. <h3>Defect Report Template</h3> In most companies, a defect reporting tool is used and the elements of a report can vary. However, in general, a defect report can consist of the following elements. While reporting the bug to developer, your Bug Report should contain the following information <ul><li style="text-align: justify;">Defect_ID - Unique identification number for the defect.</li><li style="text-align: justify;">Defect Description - Detailed description of the Defect including information about the module in which Defect was found.</li><li style="text-align: justify;">Version - Version of the application in which defect was found.</li><li style="text-align: justify;">Steps - Detailed steps along with screenshots with which the developer can reproduce the defects.</li><li style="text-align: justify;">Date Raised - Date when the defect is raised</li><li style="text-align: justify;">Reference - where in you Provide reference to the documents like. requirements, design, architecture or maybe even screenshots of the error to help understand the defect</li><li style="text-align: justify;">Detected By - Name/ID of the tester who raised the defect</li><li style="text-align: justify;">Status - Status of the defect, more on this later</li><li style="text-align: justify;">Fixed by - Name/ID of the developer who fixed it</li><li style="text-align: justify;">Date Closed - Date when the defect is closed</li><li style="text-align: justify;">Severity which describes the impact of the defect on the application</li><li style="text-align: justify;">Priority which is related to defect fixing urgency. Severity Priority could be High/Medium/Low based on the impact urgency at which the defect should be fixed respectively</li></ul> <h3 style="text-align: justify;">Reporting Defects Effectively</h3> Be specific:<ul><li style="text-align: justify;">Specify the exact action: Do not say something like ‘Select ButtonB’. Do you mean ‘Click ButtonB’ or ‘Press ALT+B’ or ‘Focus on ButtonB and click ENTER’? Of course, if the defect can be arrived at by using all the three ways, it’s okay to use a generic term as ‘Select’ but bear in mind that you might just get the fix for the ‘Click ButtonB’ scenario.</li><li style="text-align: justify;">In case of multiple paths, mention the exact path you followed: Do not say something like “If you do ‘A and X’ or ‘B and Y’ or ‘C and Z’, you get D.” Understanding all the paths at once will be difficult. Instead, say “Do ‘A and X’ and you get D.” You can, of course, mention elsewhere in the report that “D can also be got if you do ‘B and Y’ or ‘C and Z’.”</li><li style="text-align: justify;">Do not use vague pronouns: Do not say something like “In ApplicationA, open X, Y, and Z, and then close it.” What does the ‘it’ stand for? ‘Z’ or, ‘Y’, or ‘X’ or ‘ApplicationA’?”</li></ul> Be detailed:<ul><li style="text-align: justify;">Provide more information (not less). In other words, do not be lazy. Developers may or may not use all the information you provide but they sure do not want to beg you for any information you have missed.</li></ul> Be objective:<ul><li style="text-align: justify;">Do not make subjective statements like “This is a lousy application” or “You fixed it real bad.”</li><li style="text-align: justify;">Stick to the facts and avoid the emotions.</li><li style="text-align: justify;">Reproduce the defect:</li><li style="text-align: justify;">Do not be impatient and file a defect report as soon as you uncover a defect. Replicate it at least once more to be sure. (If you cannot replicate it again, try recalling the exact test condition and keep trying. However, if you cannot replicate it again after many trials, finally submit the report for further investigation, stating that you are unable to reproduce the defect anymore and providing any evidence of the defect if you had gathered.)</li></ul> Review the report:<ul><li style="text-align: justify;">Do not hit ‘Submit’ as soon as you write the report. Review it at least once. Remove any typos.</li></ul> <blockquote style="text-align: justify;">Useful Links: <a href="https://bugherd.com/blog/bug-reporting/" target="_blank" style="font-size: 14px;">Bug report article/eng</a> <a href="https://www.youtube.com/watch?v=Axm-F0pH8cg" target="_blank" style="font-size: 14px;">Bug report video tutorial/rus</a> <a href="https://www.youtube.com/watch?v=dns4zBqfpEM" target="_blank" style="font-size: 14px;">Bug report video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=g8FJ_Zja9P0" target="_blank" style="font-size: 14px;">Bug, Bug report video tutorial/arm</a> </blockquote>

Defect report is a document identifying a defect detected by a tester.

Defect Report

<h3>Test Case</h3> A TEST CASE is a set of conditions or variables under which a tester will determine whether a system under test satisfies requirements or works correctly. The process of developing test cases can also help find problems in the requirements or design of an application. <table style="border-collapse: collapse; width: 100%; text-align: justify;"><tbody>
<tr>
	<td style="width: 24.3732%;">Test Case Field </td>
	<td style="width: 75.5102%;">Description </td></tr>
<tr>
	<td>&nbsp;Test case ID: <div style="color:rgba(0,0,0,0.01);width:0;height:0">&nbsp; </div></td>
	<td>Each test case should be represented by a unique ID. To indicate test types follow some convention like "TC_UI_1" indicating "User Interface Test Case#1." </td></tr>
<tr>
	<td>&nbsp;Test Priority: <div style="color:rgba(0,0,0,0.01);width:0;height:0">&nbsp; </div></td>
	<td>&nbsp;It is useful while executing the test &nbsp;Low &nbsp;Medium &nbsp;High </td></tr>
<tr>
	<td>&nbsp;Name of the Module: </td>
	<td>&nbsp;Determine the name of the main module or sub-module being tested </td></tr>
<tr>
	<td>&nbsp;Test Designed by: </td>
	<td>&nbsp;Tester's Name </td></tr>
<tr>
	<td>&nbsp;Date of test designed: </td>
	<td>&nbsp;Date when test was designed </td></tr>
<tr>
	<td>&nbsp;Test Executed by: </td>
	<td>&nbsp;Who executed the test- tester </td></tr>
<tr>
	<td>&nbsp;Date of the Test Execution: </td>
	<td>&nbsp;Date when test needs to be executed </td></tr>
<tr>
	<td>&nbsp;Name or Test Title: </td>
	<td>&nbsp;Title of the test case </td></tr>
<tr>
	<td>&nbsp;Description/Summary of Test: </td>
	<td>&nbsp;Determine the summary or test purpose in brief </td></tr><tr>
	<td>&nbsp;Pre-condition: </td>
	<td>&nbsp;Any requirement that needs to be done before execution of this test case. To execute this test case list all pre-conditions </td></tr><tr>
	<td>&nbsp;Dependencies: </td>
	<td>&nbsp;Determine any dependencies on test requirements or other test cases </td></tr><tr>
	<td>&nbsp;Test Steps: </td>
	<td>&nbsp;Mention all the test steps in detail and write in the order in which it requires to be executed. While writing test steps ensure that you provide as much detail as you can </td></tr><tr>
	<td>&nbsp;Test Data: </td>
	<td>&nbsp;Use of test data as an input for the test case. Deliver different data sets with precise values to be used as an input </td></tr><tr>
	<td>&nbsp;Expected Results: </td>
	<td>&nbsp;Mention the expected result including error or message that should appear on screen </td></tr><tr>
	<td>&nbsp;Post-Condition: </td>
	<td>&nbsp;What would be the state of the system after running the test case? <div style="color:rgba(0,0,0,0.01);width:0;height:0">&nbsp; </div></td></tr><tr>
	<td>&nbsp;Actual Result: </td>
	<td>&nbsp;After test execution, actual test result should be filled </td></tr><tr>
	<td>&nbsp;Status (Fail/Pass): </td>
	<td>&nbsp;Mark this field as failed, if actual result is not as per the estimated result </td></tr><tr>
	<td>&nbsp;Notes: </td>
	<td>&nbsp;If there are some special condition which is left in above field </td></tr></tbody></table> <h3>Test Case vs Test Scenario</h3> <ol><li style="text-align: justify;">Test Case is a set of actions executed to verify particular features or functionality whereas Test Scenario is any functionality that can be tested.</li><li style="text-align: justify;">Test Case is mostly derived from test scenarios while Test Scenarios are derived from test artifacts like BRS and SRS.</li><li style="text-align: justify;">Test Case is mostly derived from test scenarios while Test Scenarios are derived from test artifacts like BRS and SRS.</li><li style="text-align: justify;">Test Case helps in exhaustive testing of an application whereas Test Scenario helps in an agile way of testing the end to end functionality.</li><li style="text-align: justify;">Test Cases are focused on what to test and how to test while Test Scenario is more focused on what to test.</li><li style="text-align: justify;">Test Cases are low-level actions whereas Test Scenarios are high-level actions.</li><li style="text-align: justify;">Test Case requires more resources and time for test execution while Test Scenario requires fewer resources and time for test execution.</li><li style="text-align: justify;">Test Case includes test steps, data, expected results for testing whereas Test Scenario includes an end to end functionality to be tested.</li><li style="text-align: justify;">Here, are significant differences between Test scenario and a Test Case</li></ol> <table style="border-collapse: collapse; width: 100%; text-align: justify;"><tbody>
<tr>
	<td style="width: 50%;">Test Scenario </td>
	<td style="width: 50%;">Test Case </td></tr>
<tr>
	<td style="width: 50%;">A test scenario contains high-level documentation which describes an end to end functionality to be tested. </td>
	<td style="width: 50%;">Test cases contain definite test steps, data, expected results for testing all the features of an application. </td></tr>
<tr>
	<td style="width: 50%;">It focuses on more "what to test" than "how to test". </td>
	<td style="width: 50%;">A complete emphasis on "what to test" and "how to test.". </td></tr>
<tr>
	<td style="width: 50%;">Test scenarios are a one-liner. So, there is always the possibility of ambiguity during the testing․ </td>
	<td style="width: 50%;">Test cases have defined a step, pre-requisites, expected result, etc. Therefore, there is no ambiguity in this process. </td></tr>
<tr>
	<td style="width: 50%;">Test scenarios are derived from test artifacts like BRS, SRS, etc. </td>
	<td style="width: 50%;">Test case is mostly derived from test scenarios. Multiple Test case can be derived from a single Test Scenario․ </td></tr>
<tr>
	<td style="width: 50%;">It helps in an agile way of testing the end-to-end functionality․ </td>
	<td style="width: 50%;">It helps in exhaustive testing of an application․ </td></tr>
<tr>
	<td style="width: 50%;">Test scenarios are high-level actions. </td>
	<td style="width: 50%;">Test cases are low-level actions. </td></tr>
<tr>
	<td style="width: 50%;">Comparatively less time and resources are required for creating &amp; testing using scenarios. </td>
	<td style="width: 50%;">More resources are needed for documentation and execution of test cases. </td></tr>

</tbody></table> <blockquote style="text-align: justify;">Useful Links: <a href="https://www.guru99.com/test-case.html" target="_blank" style="font-size: 14px;">Test case article/eng</a> <a href="https://www.parasoft.com/blog/how-to-write-test-cases-for-software-examples-tutorial/" target="_blank" style="font-size: 14px;">Test case article/eng</a> <a href="https://www.youtube.com/watch?v=e0cHqx5cRPo" target="_blank" style="font-size: 14px;">Test case video tutorial/rus</a> <a href="https://www.youtube.com/watch?v=g0PrXoWKM2Y" target="_blank" style="font-size: 14px;">Test case video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=Hq7dt5zVxL0" target="_blank" style="font-size: 14px;">Test case, Test plan video tutorial/arm</a> </blockquote>

Test Case

<h3>Test Script</h3> A TEST SCRIPT is a set of instructions (written using a scripting/programming language) that is performed on a system under test to verify that the system performs as expected. Test scripts are used in automated testing. Sometimes, a set of instructions (written in a human language), used in manual testing, is also called a Test Script but a better term for that would be a Test Case. Some scripting languages used in automated testing are:<ol><li style="text-align: justify;">JavaScript</li><li style="text-align: justify;">Perl</li><li style="text-align: justify;">Python</li><li style="text-align: justify;">Ruby</li><li style="text-align: justify;">Tcl</li><li style="text-align: justify;">Unix Shell Script</li><li style="text-align: justify;">VBScript</li></ol> <blockquote style="text-align: justify;">Useful Links: <a href="https://www.guru99.com/test-script.html" target="_blank" style="font-size: 14px;">Test script article/eng</a> <a href="https://www.youtube.com/watch?v=txQZm6l4MbM" target="_blank">Test script video tutorial/eng</a> </blockquote>

Test Script as a part of testing documentation.

Test Script

<h3>Test Plan</h3> A TEST PLAN is a document describing software testing scope and activities. It is the basis for formally testing any software/product in a project. <h3>Test Plan Template</h3> Test Plan Identifier:<ul><li style="text-align: justify;">Every test plan must have a unique Identifier that may contain information about the version, type of the test plan, etc. for example: ‘Master Test plan for Workshop Module TP_1.0’ :</li></ul> Introduction:<ul><li style="text-align: justify;">Provide an overview of the test plan.</li><li style="text-align: justify;">Specify the goals/objectives.</li><li style="text-align: justify;">Specify any constraints.</li></ul> References:<ul><li style="text-align: justify;">List the related documents, with links to them if available, including the following:</li><li style="text-align: justify;">Project Plan</li><li style="text-align: justify;">Configuration Management Plan</li></ul> Test Items:<ul><li style="text-align: justify;">List the test items (software/products) and their versions.</li></ul> Features to be Tested:<ul><li style="text-align: justify;">List the features of the software/product to be tested.</li><li style="text-align: justify;">Provide references to the Requirements and/or Design specifications of the features to be tested</li></ul> Features Not to Be Tested:<ul><li style="text-align: justify;">List the features of the software/product which will not be tested.</li><li style="text-align: justify;">Specify the reasons these features won’t be tested.</li></ul> Approach:<ul><li style="text-align: justify;">Mention the overall approach to testing.</li><li style="text-align: justify;">Specify the testing levels [if it’s a Master Test Plan], the testing types, and the testing methods [Manual/Automated; White Box/Black Box/Gray Box]</li></ul> Item Pass/Fail Criteria:<ul><li style="text-align: justify;">Specify the criteria that will be used to determine whether each test item (software/product) has passed or failed testing.</li></ul> Suspension Criteria and Resumption Requirements:<ul><li style="text-align: justify;">Specify criteria to be used to suspend the testing activity.</li><li style="text-align: justify;">Specify testing activities which must be redone when testing is resumed.</li></ul> Test Deliverables:<ul><li style="text-align: justify;">List test deliverables, and links to them if available, including the following:</li><li style="text-align: justify;">Test Plan (this document itself)</li><li style="text-align: justify;">Test Cases</li><li style="text-align: justify;">Test Scripts</li><li style="text-align: justify;">Defect/Enhancement Logs</li><li style="text-align: justify;">Test Reports</li></ul> Test Environment:<ul><li style="text-align: justify;">Specify the properties of test environment: hardware, software, network etc.</li><li style="text-align: justify;">List any testing or related tools․</li></ul> Estimate:<ul><li style="text-align: justify;">Provide a summary of test estimates (cost or effort) and/or provide a link to the detailed estimation.</li></ul> Schedule:<ul><li style="text-align: justify;">Provide a summary of the schedule, specifying key test milestones, and/or provide a link to the detailed schedule.</li></ul> Staffing and Training Needs:<ul><li style="text-align: justify;">Specify staffing needs by role and required skills.</li><li style="text-align: justify;">Identify training that is necessary to provide those skills, if not already acquired.</li></ul> Responsibilities:<ul><li style="text-align: justify;">List the responsibilities of each team/role/individual.</li></ul> Risks:<ul><li style="text-align: justify;">List the risks that have been identified.</li><li style="text-align: justify;">Specify the mitigation plan and the contingency plan for each risk.</li></ul> Assumptions and Dependencies:<ul><li style="text-align: justify;">List the assumptions that have been made during the preparation of this plan.</li><li style="text-align: justify;">List the dependencies.</li></ul> Approvals:<ul><li style="text-align: justify;">Specify the names and roles of all persons who must approve the plan.</li><li style="text-align: justify;">Provide space for signatures and dates. (If the document is to be printed.</li></ul> <blockquote style="text-align: justify;"> Useful Links։ <a href="https://www.guru99.com/what-everybody-ought-to-know-about-test-planing.html" target="_blank">Test plan article/eng</a> <a href="https://www.youtube.com/watch?v=S2_AJP9Oeg0" target="_blank">Test plan video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=KH7oPMlAaSM" target="_blank">Test plan video tutorial/rus</a> <a href="https://www.youtube.com/watch?v=Hq7dt5zVxL0" target="_blank">Test plan, Test case video tutorial/arm</a></blockquote>

Test Plan is an important document describing the process of software testing. 

Test Plan

<h3>Agile Model</h3> Agile is a coding practice that follows the rules and principles of agile software development. In this Agile Tutorial, you will learn the fundamentals of Agile, Agile models and methodologies, Agile Vs. Scrum differences, Scrum master training to Agile testing interview questions &amp; answers. This Agile development tutorial is an absolute beginners guide to Agile, and Scrum testing, Basic understanding of manual or automation software testing will be beneficial. <h3>How does Agile work?</h3> <ul><li style="text-align: justify;">You make a list</li><li style="text-align: justify;">You size things up</li><li style="text-align: justify;">You set some priorities</li><li style="text-align: justify;">You start executing</li><li style="text-align: justify;">You update the plan as you go</li></ul> <h3>How is Agile different?</h3> <ul><li style="text-align: justify;">Analysis, design, coding, and testing are continuous activities</li><li style="text-align: justify;">Development is iterative</li><li style="text-align: justify;">Planning is adaptive</li><li style="text-align: justify;">Roles blur</li><li style="text-align: justify;">Scope can vary</li><li style="text-align: justify;">Requirements can change</li><li style="text-align: justify;">Working software is the primary measure of success</li></ul> <h3>User stories and estimation</h3> <ul><li style="text-align: justify;">User stories are features our customers might one day like to see in their software.</li><li style="text-align: justify;">They are written on index cards to encourage face-to-face communication.</li><li style="text-align: justify;">Typically no more than a couple days work, they form the basis of our Agile plans.</li><li style="text-align: justify;">We get them by sitting down with our customers and asking lots of questions.</li></ul> <h3>Iterations</h3> Iterations are the basic building block of Agile development. Each iteration is a standard, fixed-length timebox, where Agile Teams deliver incremental value in the form of working, tested software and systems. The recommended duration of the timebox is two weeks. However, one to four weeks is acceptable, depending on the business context. Iterations provide a regular, predictable cadence for teams to produce an increment of value, as well as to refine those previously developed. These short time periods help the team, Product Owners, Product Managers, and other stakeholders regularly test and evaluate the technical and business hypotheses in a working system. Each iteration anchors an integration point, a ‘pull event’ that assembles various system aspects—functionality, quality, alignment, and fitness for use—across all the teams’ contributions. Since the shortest sustainable lead time is a significant goal of Lean-Agile development, Agile teams execute a full plan-do-check-adjust (PDCA) cycle as quickly as possible. The PDCA learning cycle (shown in Figure 1) represents the following iteration events: <ul><li style="text-align: justify;">Plan –Iteration Planning is the plan step </li><li style="text-align: justify;">Do – Iteration Execution is the do step</li><li style="text-align: justify;">Check – Iteration Review is the check step</li><li style="text-align: justify;">Adjust – Iteration Retrospective is the adjust step</li></ul> <h3>Planning and Refactoring</h3> <ul><li style="text-align: justify;">Master Story - Our to-do list on an agile project</li><li style="text-align: justify;">Team Velocity - The speed at which we turn user stories into working software</li><li style="text-align: justify;">Planning - iterations = total effort / estimated team velocity</li><li style="text-align: justify;">Refactoring - As we add more functionality to the system we need a way of maintaining our design and keeping our house in order.</li></ul> <blockquote style="text-align: justify;">Useful Links: <a href="https://www.infoworld.com/article/3237508/what-is-agile-methodology-modern-software-development-explained.html" target="_blank" style="font-size: 14px;">Agile methodology article/eng</a> <a href="https://scrumtrek.ru/blog/agile-scrum/4029/metodologiya-agile/" target="_blank">Agile methodology article/rus</a> <a href="https://www.youtube.com/watch?v=WjwEh15M5Rw" target="_blank">Agile methodology video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=TPrj-AMJ4Ds" target="_blank">Agile methodology video tutorial/rus</a> </blockquote>

What is Agile Model and how does it work?

Agile Model

<h3>Agile VS Waterfall</h3> Key Difference Waterfall is a Liner Sequential Life Cycle Model whereas Agile is a continuous iteration of development and testing in the software development process.In Agile vs Waterfall difference, the Agile methodology is known for its flexibility whereas Waterfall is a structured software development methodology.Comparing the Waterfall methodology vs Agile which follows an incremental approach whereas the Waterfall is a sequential design process.Agile performs testing concurrently with software development whereas in Waterfall methodology testing comes after the “Build” phase.Agile allows changes in project development requirement whereas Waterfall has no scope of changing the requirements once the project development starts. <table style="border-collapse: collapse; width: 100%; text-align: justify;"><tbody>
<tr>
	<td style="width: 50%;">Agile </td>
	<td style="width: 50%;">Waterfall </td></tr>
<tr>
	<td style="width: 50%;">It separates the project development lifecycle into sprints. </td>
	<td style="width: 50%;">Software development process is divided into distinct phases. </td></tr>
<tr>
	<td style="width: 50%;">It follows an incremental approach. </td>
	<td style="width: 50%;">Waterfall methodology is a sequential design process. </td></tr>
<tr>
	<td style="width: 50%;">Agile methodology is known for its flexibility. </td>
	<td style="width: 50%;">Waterfall is a structured software development methodology so most times it can be quite rigid. </td></tr>
<tr>
	<td style="width: 50%;">Agile can be considered as a collection of many different projects. </td>
	<td style="width: 50%;">Software development will be completed as one single project. </td></tr>
<tr>
	<td style="width: 50%;">Agile is quite a flexible method which allows changes to be made in the project development requirements even if the initial planning has been completed. <div style="color:rgba(0,0,0,0.01);width:0;height:0">&nbsp; </div></td>
	<td style="width: 50%;">There is no scope of changing the requirements once the project development starts. </td></tr>
<tr>
	<td style="width: 50%;">Agile methodology, follow an iterative development approach because of this planning, development, prototyping and other software development phases may appear more than once. </td>
	<td style="width: 50%;">All the project development phases like designing, development, testing, etc. are completed once in the Waterfall model. </td></tr>
<tr>
	<td style="width: 50%;">Test plan is reviewed after each sprint <div style="color:rgba(0,0,0,0.01);width:0;height:0">&nbsp; </div></td>
	<td style="width: 50%;">The test plan is rarely discussed during the test phase. </td></tr>
<tr>
	<td style="width: 50%;">Agile development is a process in which the requirements are expected to change and evolve. </td>
	<td style="width: 50%;">The method is ideal for projects which have definite requirements and changes not at all expected. </td></tr>
<tr>
	<td style="width: 50%;">In Agile methodology, testing is performed concurrently with software development. </td>
	<td style="width: 50%;">In this methodology, the "Testing" phase comes after the "Build" phase </td></tr><tr>
	<td style="width: 50%;">Agile introduces a product mindset where the software product satisfies needs of its end customers and changes itself as per the customer's demands. </td>
	<td style="width: 50%;">This model shows a project mindset and places its focus completely on accomplishing the project. </td></tr><tr>
	<td style="width: 50%;">Agile methdology works exceptionally well with Time &amp; Materials or non-fixed funding. It may increase stress in fixed-price scenarios. </td>
	<td style="width: 50%;">Reduces risk in the firm fixed price contracts by getting risk agreement at the beginning of the process. </td></tr><tr>
	<td style="width: 50%;">Prefers small but dedicated teams with a high degree of coordination and synchronization. </td>
	<td style="width: 50%;">Team coordination/synchronization is very limited. </td></tr><tr>
	<td style="width: 50%;">Products owner with team prepares requirements just about every day during a project. </td>
	<td style="width: 50%;">Business analysis prepares requirements before the beginning of the project. </td></tr><tr>
	<td style="width: 50%;">Test team can take part in the requirements change without problems. </td>
	<td style="width: 50%;">It is difficult for the test to initiate any change in requirements. </td></tr><tr>
	<td style="width: 50%;">Description of project details can be altered anytime during the SDLC process. </td>
	<td style="width: 50%;">Detail description needs to implement waterfall software development approach. </td></tr><tr>
	<td style="width: 50%;">The Agile Team members are interchangeable, as a result, they work faster. There is also no need for project managers because the projects are managed by the entire team </td>
	<td style="width: 50%;">In the waterfall method, the process is always straightforward so, project manager plays an essential role during every stage of SDLC. </td></tr></tbody></table> <blockquote style="text-align: justify;">Useful links: <a href="https://worksection.com/blog/waterfall-vs-agile.html" target="_blank">Agile vs Waterfall article/rus</a> <a href="https://www.youtube.com/watch?v=rvTejAg_fbY" target="_blank">Agile vs Waterfall video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=P6RKvbB2Br8" target="_blank">Agile vs Waterfall video tutorial/rus</a></blockquote>

What is the difference between Agile and Waterfall models?

Agile VS Waterfall

<h3>Scrum Methodology</h3> Scrum Master The Scrum Master helps the Scrum Team perform at their highest level. They also protect the team from both internal and external distractions. Product Owner The Product Owner is expected to do the best possible job of satisfying all stakeholders, maintain the Product Backlog, and ensure that everyone knows the priorities. The Development Team Development Teams are structured and empowered to organize and manage their own work. The resulting synergy optimizes overall efficiency and effectiveness. Backlog The Product Backlog is an ordered list of everything that is known to be needed in a product. It is constantly evolving and is never complete. The Sprint The heart of Scrum is a Sprint, during which a useable and potentially releasable product Increment is created. Sprints can be one week to one month in length and happen one right after the other to keep projects moving. There are four events that happen with each Sprint: <ul><li style="text-align: justify;">Sprint Planning – The Team decides what to work on for the current period.</li><li style="text-align: justify;">Daily Scrum – The Development Team meets for 15 minutes (or less) every day of the Sprint to inspect progress toward the Sprint Goal.</li><li style="text-align: justify;">Sprint Review – The Team collaborates about what was done and adapts the Backlog as needed.</li><li style="text-align: justify;">Sprint Retrospective – The Team discusses what went right, what went wrong, and how to improve.</li></ul> <blockquote style="text-align: justify;">Useful Links: <a href="https://www.atlassian.com/agile/scrum" target="_blank" style="font-size: 14px;">Scrum methodology article/eng</a> <a href="https://www.atlassian.com/ru/agile/scrum" target="_blank" style="font-size: 14px;">Scrum methodology article/rus</a> <a href="https://www.youtube.com/watch?v=8dGdIcyDk1w" target="_blank" style="font-size: 14px;">Scrum methodology video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=mockcEwNBbs" target="_blank" style="font-size: 14px;">Scrum methodology video tutorial/rus</a></blockquote>

Scrum Methodology

<h3>Kanban Methodology</h3> Visualize what you do today (workflow): seeing all the items in context of each other can be very informative Limit the amount of work in progress (WIP): this helps balance the flowbased approach so teams dont start and commit to too much work at once Enhance flow: when something is finished, the next highest thing from the backlog is pulled into play <blockquote style="text-align: justify;">Useful Links: <a href="https://www.atlassian.com/agile/kanban" target="_blank">Kanban methodology article/eng</a> <a href="https://upr.ru/article/metodologiya-kanban-sekrety-effektivnogo-ispolzovaniya/" target="_blank">Kanban methodology article/rus</a> <a href="https://www.youtube.com/watch?v=1_Zti9v5ugA" target="_blank">Kanban methodology video tutorial/rus</a> <a href="https://www.youtube.com/watch?v=iVaFVa7HYj4" target="_blank">Kanban methodology video tutorial/eng</a></blockquote>

Kanban Methodology

<h3>Scrum VS Kanban</h3> <table style="border-collapse:collapse;width: 100%;"><tbody>
<tr>
	<td style="width: 50%; text-align: center;">Scrum </td>
	<td style="width: 50%; text-align: center;">Kanban </td></tr>
<tr>
	<td style="width: 50%;">Scrum stresses on planning. It starts with sprint planning and ends up with sprint retrospective. There are many meetings held which help to assure that the team is aligned with the next steps, priorities, and learnings from previous sprints. </td>
	<td style="width: 50%;">Kanban is open to making changes on the go. It means there is less rigidity and things can change frequently. </td></tr>
<tr>
	<td style="width: 50%;">It recommends collection of time measurements made during sprints. </td>
	<td style="width: 50%;">Kanban recommends graphs to get an overview of team's progress over time. </td></tr>
<tr>
	<td style="width: 50%;">Scrum no longer asks for a commitment from teams. Instead, it is about the sprint goals and forecasts. </td>
	<td style="width: 50%;">Kanban relies on time-boxing and forecasts. </td></tr>
<tr>
	<td style="width: 50%;">It stresses on planning, and so estimation has a very important role in Scrum </td>
	<td style="width: 50%;">Kanban has no mandatory requirements for estimation. </td></tr>
<tr>
	<td style="width: 50%;">Every individual has their role and responsibilities. </td>
	<td style="width: 50%;">No set roles so flexibility in term of individual responsibilities. </td></tr>
<tr>
	<td style="width: 50%;">The iterations/Sprints are fixed in duration. This duration varies from 2 weeks to 1 month. </td>
	<td style="width: 50%;">Kanban is not based on duration. This thing is measured regarding Cycle times. </td></tr>
<tr>
	<td style="width: 50%;">Teams are required to commit a specific amount of work. </td>
	<td style="width: 50%;">Commitment not necessary it is optional for teams </td></tr>
<tr>
	<td style="width: 50%;">In this method, cross-functional teams are important as they can deal with any disruption that may cause a bottleneck in the software development. </td>
	<td style="width: 50%;">Having specialized team is important. </td></tr>
<tr>
	<td style="width: 50%;">It is not possible to add items to ongoing iterations. </td>
	<td style="width: 50%;">New items can easily add if the additional capacity is available. </td></tr><tr>
	<td style="width: 50%;">A sprint backlog is owned by only by a single team. </td>
	<td style="width: 50%;">Multiple teams can share Kanban board. </td></tr><tr>
	<td style="width: 50%;">Deliverables are determined by sprints, which a set of work must be completed and ready for review. </td>
	<td style="width: 50%;">Products and processes are delivered continuously on a needed basis. So testing and review process goes on simultaneously. </td></tr><tr>
	<td style="width: 50%;">Scrum software development method focuses on the backlog. </td>
	<td style="width: 50%;">Kanban method entirely focuses on process dashboard. </td></tr><tr>
	<td style="width: 50%;">Every team member has a specific role in Scrum master decide timelines, product owner set goals and objectives, and team members conduct the development work. </td>
	<td style="width: 50%;">There are no pre-defined roles for a team. However, there may still be a Project Manager; the team is encouraged to collaborate and works together. </td></tr><tr>
	<td style="width: 50%;">Best for projects with changing priorities. </td>
	<td style="width: 50%;">Ideal for teams with stable priorities that unlikely to change over time. </td></tr><tr>
	<td style="width: 50%;">Measures production using velocity through sprints. </td>
	<td style="width: 50%;">Measures production using cycle time or the exact time it takes to complete one full piece of a project. </td></tr><tr>
	<td style="width: 50%;">Scrum requires a complete shift from the traditional model to the Agile Scrum model that would be implemented the project. </td>
	<td style="width: 50%;">Kanban doesn't allow drastic changes in the project. </td></tr><tr>
	<td style="width: 50%;">It is an ideal method for projects with widely-varying priorities. </td>
	<td style="width: 50%;">Best suitable for teams with stable priorities. </td></tr><tr>
	<td style="width: 50%;">In Scrum, the entire team focuses on to collaborate and complete the task to provide quality development work. </td>
	<td style="width: 50%;">Teams work to achieve goals and reduce the time to complete the entire process. Thus, reduction in the time cycle is biggest indicators of success here. </td></tr><tr>
	<td style="width: 50%;">Scrum emphasis on its schedules; new items cannot be added to ongoing iterations. </td>
	<td style="width: 50%;">Kanban is more iterative by nature as it does not have specific timeframes. So that, new items can be continually added whenever additional capacity is available. </td></tr></tbody></table> <blockquote>Useful Links: <a href="https://www.guru99.com/scrum-vs-kanban.html" target="_blank" style="font-size: 14px;">Scrum vs Kanban article/eng</a> <a href="https://asana.com/ru/resources/waterfall-agile-kanban-scrum" target="_blank" style="font-size: 14px;">Scrum vs Kanban article/rus</a> <a href="https://www.youtube.com/watch?v=GLFuzBiy18o" target="_blank" style="font-size: 14px;">Scrum vs Kanban video tutorial/eng</a></blockquote>

Differences between two Agile methodologies: Scrum and Kanban.

Scrum VS Kanban

<h3>Terminology</h3> WWW (Word Wide Web) - World Wide Web, which is also known as a Web, is a collection of websites or web pages stored in web servers and connected to local computers through the internet. These websites contain text pages, digital images, audios, videos, etc. Users can access the content of these sites from any part of the world over the internet using their devices such as computers, laptops, cell phones, etc. The WWW, along with internet, enables the retrieval and display of text and media to your device. URI (Uniform Resource Identifier) -A URI is a string containing characters that identify a physical or logical resource. URI follows syntax rules to ensure uniformity. Moreover, it also maintains extensibility via a hierarchical naming scheme. The full form of URI is Uniform Resource Identifier. URN (Uniform Resource Name) - Uniform Resource Name (URN) is an internet resource that specifies URN scheme. URL (Uniform Resource Locator) – A URL is a global address of documents and protocols to retrieve resource on a computer network. URLs occur most frequently in reference to web pages (HTTP) but can also be used for database access using JDBC, email (mailto), file transfer (FTP), and many other applications. URL stands for Uniform Resource Locator. Web Browser – "A web browser, or simply 'browser,' is an application used to access and view websites. Web Server - A web server is a computer that runs websites. It's a computer program that distributes web pages as they are requisitioned. The basic objective of the web server is to store, process and deliver web pages to the users. This intercommunication is done using Hypertext Transfer Protocol (HTTP). Web Page – A document which can be displayed in a web browser such as Firefox, Google Chrome, Opera, Microsoft Internet Explorer or Edge, or Apple's Safari. These are also often called just "pages." website. A collection of web pages which are grouped together and usually connected together in various ways. Web Site – a group of World Wide Web pages usually containing hyperlinks to each other and made available online by an individual, company, educational institution, government, or organization The client side is visible to the user, but the server side is not. <h3>Protocols</h3> Below are the 4 main protocols: <ul><li style="text-align: justify;">IP (Internet Protocol)</li><li style="text-align: justify;">FTP (File Transfer Protocol)</li><li style="text-align: justify;">HTTP (Hypertext Transfer Protocol)</li><li style="text-align: justify;">HTTPS (Hypertext Transfer Protocol Secure)</li></ul> Cash - A temporary storage area in memory or on disk that holds the most recently downloaded Web pages. As you jump from Web page to Web page, caching those pages in memory lets you quickly go back to a page without having to download it from the Web again. Cookie - Cookies are text files with small pieces of data — like a username and password — that are used to identify your computer as you use a computer network. Specific cookies known as HTTP cookies are used to identify specific users and improve your web browsing experience. Authentication - Authentication is the act of validating that users are whom they claim to be. This is the first step in any security process. Giving someone permission to download a particular file on a server or providing individual users with administrative access to an application are good examples of authentication. Authorization - Authorization in a system security is the process of giving the user permission to access a specific resource or function. This term is often used interchangeably with access control or client privilege. In secure environments, authorization must always follow authentication. Users should first prove that their identities are genuine before an organization’s administrators grant them access to the requested resources. <h3>HTTP(S) Methods</h3> <table style="border-collapse: collapse; width: 100.281%; text-align: justify;"><tbody>
<tr>
	<td style="width: 10.201%;">HTTP Verb </td>
	<td style="width: 14.0704%;">CRUD </td>
	<td style="width: 38.5427%;">Entire Collection (e.g. /customers) </td>
	<td style="width: 37.1357%;">Specific Item (e.g. /customers/{id}) </td></tr>
<tr>
	<td>POST <div style="color:rgba(0,0,0,0.01);width:0;height:0">&nbsp; </div></td>
	<td>Create </td>
	<td>201 (Created), 'Location' header with link to /customers/{id} containing new ID. </td>
	<td>404 (Not Found), 409 (Conflict) if resource already exists.. </td></tr>
<tr>
	<td>GET </td>
	<td>Read </td>
	<td>200 (OK), list of customers. Use pagination, sorting and filtering to navigate big lists. </td>
	<td>200 (OK), single customer. 404 (Not Found), if ID not found or invalid. </td></tr>
<tr>
	<td>PUT </td>
	<td>Update/Replace </td>
	<td>405 (Method Not Allowed), unless you want to update/replace every resource in the entire collection. </td>
	<td>200 (OK) or 204 (No Content). 404 (Not Found), if ID not found or invalid. </td></tr>
<tr>
	<td>PATCH </td>
	<td>Update/Modify </td>
	<td>405 (Method Not Allowed), unless you want to modify the collection itself. </td>
	<td>200 (OK) or 204 (No Content). 404 (Not Found), if ID not found or invalid. </td></tr><tr>
	<td>DELETE </td>
	<td>Delete </td>
	<td>405 (Method Not Allowed), unless you want to delete the whole collection—not often desirable. </td>
	<td>200 (OK). 404 (Not Found), if ID not found or invalid. </td></tr></tbody></table> <blockquote style="text-align: justify;">Useful Links: <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP" target="_blank">HTTP Basics article/eng</a> <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods" target="_blank">HTTP methods article/rus</a> <a href="https://www.youtube.com/watch?v=eesqK59rhGA" target="_blank">HTTP and WEB video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=9aycvfzH8UA" target="_blank">HTTP video tutorial/rus</a> <a href="https://www.youtube.com/watch?v=FsE0W7_l3uo" target="_blank">HTTP response video tutorial/arm</a></blockquote>

What is the role of web technologies in QA.

The role of web technologies in QA

<h3>Regular Expression</h3>
 <img src="https://lh4.googleusercontent.com/O5bWLkMcrUEwsqT2cy5oWr4R01dMpmVNrl4x60H3NEV5dj6kj0tW4sWGy7WNULq2cOA2N993YgbCuraUDhzAWyHS0t46zKCpeoQnTXFFTWFzQX0QytZSlgWSmmk2lg161ZvQFYUlrFr_R1ooDtyTh1M7YDfok4R3jjxPTLV2Q7oz4AUq81jVYMz6kcxbTDNzT3guy9Lw" width="633" height="757" style="margin-left:0px;margin-top:0px;">
 
<blockquote> Useful Links: <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_Expressions" target="_blank">Regular expressions article/eng</a> <a href="https://developer.mozilla.org/ru/docs/Web/JavaScript/Guide/Regular_Expressions" target="_blank">Regular expressions article/rus</a> <a href="https://www.youtube.com/watch?v=sa-TUpSx1JA" target="_blank">Regular expressions video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=_pLpx6btq6U" target="_blank">Regular expressions video tutorial/rus</a></blockquote>

Regular expressions

<h3>Linux</h3>
 
Linux is an operating system's kernel. You might have heard of UNIX. Well, Linux is a UNIX clone. But it was actually created by Linus Torvalds from Scratch. Linux is free and open-source, that means that you can simply change anything in Linux and redistribute it in your own name! There are several Linux Distributions, commonly called “distros”.
 
<ol>
 <li style="text-align: justify;">Ubuntu Linux</li>
 <li style="text-align: justify;">Red Hat Enterprise Linux</li>
 <li style="text-align: justify;">Linux Mint</li>
 <li style="text-align: justify;">Debian</li>
 <li style="text-align: justify;">Fedora</li>
</ol>
 
Linux is Mainly used in servers. About 90% of the internet is powered by Linux servers. This is because Linux is fast, secure, and free! The main problem of using Windows servers are their cost. This is solved by using Linux servers. The OS that runs in about 80% of the smartphones in the world, Android, is also made from the Linux kernel. Most of the viruses in the world run on Windows, but not on Linux! So, basically, a shell is a program that receives commands from the user and gives it to the OS to process, and it shows the output. Linux's shell is its main part. Its distros come in GUI (graphical user interface), but basically, Linux has a CLI (command line interface). In this tutorial, we are going to cover the basic commands that we use in the shell of Linux. To open the terminal, press Ctrl+Alt+T in Ubuntu, or press Alt+F2, type in gnome-terminal, and press enter. In Raspberry Pi, type in lxterminal. There is also a GUI way of taking it, but this is better!
 
<h3>Linux Basic Commands</h3>
 
pwd — When you first open the terminal, you are in the home directory of your user. To know which directory you are in, you can use the “pwd” command. It gives us the absolute path, which means the path that starts from the root. The root is the base of the Linux file system. It is denoted by a forward slash( / ). The user directory is usually something like "/home/username".
 

 
ls — Use the "ls" command to know what files are in the directory you are in. You can see all the hidden files by using the command “ls -a”.
 

 
cd — Use the "cd" command to go to a directory. For example, if you are in the home folder, and you want to go to the downloads folder, then you can type in “cd Downloads”. Remember, this command is case sensitive, and you have to type in the name of the folder exactly as it is. But there is a problem with these commands. Imagine you have a folder named “Raspberry Pi”. In this case, when you type in “cd Raspberry Pi”, the shell will take the second argument of the command as a different one, so you will get an error saying that the directory does not exist. Here, you can use a backward slash. That is, you can use “cd Raspberry Pi” in this case. Spaces are denoted like this: If you just type “cd” and press enter, it takes you to the home directory. To go back from a folder to the folder before that, you can type “cd ..” . The two dots represent back.
 

 
mkdir &amp; rmdir — Use the mkdir command when you need to create a folder or a directory. For example, if you want to make a directory called “DIY”, then you can type “mkdir DIY”. Remember, as told before, if you want to create a directory named “DIY Hacking”, then you can type “mkdir DIY Hacking”. Use rmdir to delete a directory. But rmdir can only be used to delete an empty directory. To delete a directory containing files, use rm.
 

 
rm - Use the rm command to delete files and directories. Use "rm -r" to delete just the directory. It deletes both the folder and the files it contains when using only the rm command.
 

 
touch — The touch command is used to create a file. It can be anything, from an empty txt file to an empty zip file. For example, “touch new.txt”.
 

 
man &amp; --help — To know more about a command and how to use it, use the man command. It shows the manual pages of the command. For example, “man cd” shows the manual pages of the cd command. Typing in the command name and the argument helps it show which ways the command can be used (e.g., cd –help).
 

 
cp — Use the cp command to copy files through the command line. It takes two arguments: The first is the location of the file to be copied, the second is where to copy.
 

 
mv — Use the mv command to move files through the command line. We can also use the mv command to rename a file. For example, if we want to rename the file “text” to “new”, we can use “mv text new”. It takes the two arguments, just like the cp command.
 

 
locate — The locate command is used to locate a file in a Linux system, just like the search command in Windows. This command is useful when you don't know where a file is saved or the actual name of the file. Using the -i argument with the command helps to ignore the case (it doesn't matter if it is uppercase or lowercase). So, if you want a file that has the word “hello”, it gives the list of all the files in your Linux system containing the word "hello" when you type in “locate -i hello”. If you remember two words, you can separate them using an asterisk (*). For example, to locate a file containing the words "hello" and "this", you can use the command “locate -i *hello*this”.
 

 
<h3>Intermediate Commands</h3>
 
<ul>
 <li style="text-align: justify;">echo — The "echo" command helps us move some data, usually text into a file. For example, if you want to create a new text file or add to an already made text file, you just need to type in, “echo hello, my name is alok &gt;&gt; new.txt”. You do not need to separate the spaces by using the backward slash here, because we put in two triangular brackets when we finish what we need to write.</li>
 <li style="text-align: justify;">cat — Use the cat command to display the contents of a file. It is usually used to easily view programs.</li>
</ul>
 

 
<ul>
 <li style="text-align: justify;">nano, vi, jed — nano and vi are already installed text editors in the Linux command line. The nano command is a good text editor that denotes keywords with color and can recognize most languages. And vi is simpler than nano. You can create a new file or modify a file using this editor. For example, if you need to make a new file named "check.txt", you can create it by using the command “nano check.txt”. You can save your files after editing by using the sequence Ctrl+X, then Y (or N for no). In my experience, using nano for HTML editing doesn't seem as good, because of its color, so I recommend jed text editor. We will come to installing packages soon.</li>
</ul>
 

 
<ul>
 <li style="text-align: justify;">sudo — A widely used command in the Linux command line, sudo stands for "SuperUser Do". So, if you want any command to be done with administrative or root privileges, you can use the sudo command. For example, if you want to edit a file like viz. alsa-base.conf, which needs root permissions, you can use the command – sudo nano alsa-base.conf. You can enter the root command line using the command “sudo bash”, then type in your user password. You can also use the command “su” to do this, but you need to set a root password before that. For that, you can use the command “sudo passwd”(not misspelled, it is passwd). Then type in the new root password.</li>
</ul>
 

 
<ul>
 <li style="text-align: justify;">df — Use the df command to see the available disk space in each of the partitions in your system. You can just type in df in the command line and you can see each mounted partition and their used/available space in % and in KBs. If you want it shown in megabytes, you can use the command “df -m”.</li>
</ul>
 

 
<ul>
 <li style="text-align: justify;">du — Use du to know the disk usage of a file in your system. If you want to know the disk usage for a particular folder or file in Linux, you can type in the command df and the name of the folder or file. For example, if you want to know the disk space used by the documents folder in Linux, you can use the command “du Documents”. You can also use the command “ls -lah” to view the file sizes of all the files in a folder.</li>
</ul>
 

 
<ul>
 <li style="text-align: justify;">tar — Use tar to work with tarballs (or files compressed in a tarball archive) in the Linux command line. It has a long list of uses. It can be used to compress and uncompress different types of tar archives like .tar, .tar.gz, .tar.bz2,etc. It works on the basis of the arguments given to it. For example, "tar -cvf" for creating a .tar archive, -xvf to untar a tar archive, -tvf to list the contents of the archive, etc. Since it is a wide topic, here are some examples of tar commands.</li>
 <li style="text-align: justify;">zip, unzip — Use zip to compress files into a zip archive, and unzip to extract files from a zip archive.</li>
 <li style="text-align: justify;">uname — Use uname to show the information about the system your Linux distro is running. Using the command “uname -a” prints most of the information about the system. This prints the kernel release date, version, processor type, etc.</li>
</ul>
 
&lt;
 
<ul>
 <li style="text-align: justify;">apt-get — Use apt to work with packages in the Linux command line. Use apt-get to install packages. This requires root privileges, so use the sudo command with it. For example, if you want to install the text editor jed (as I mentioned earlier), we can type in the command “sudo apt-get install jed”. Similarly, any packages can be installed like this. It is good to update your repository each time you try to install a new package. You can do that by typing “sudo apt-get update”. You can upgrade the system by typing “sudo apt-get upgrade”. We can also upgrade the distro by typing “sudo apt-get dist-upgrade”. The command “apt-cache search” is used to search for a package. If you want to search for one, you can type in “apt-cache search jed”(this doesn't require root).</li>
</ul>
 

 
<ul>
 <li style="text-align: justify;">chmod — Use chmod to make a file executable and to change the permissions granted to it in Linux. Imagine you have a python code named numbers.py in your computer. You'll need to run “python numbers.py” every time you need to run it. Instead of that, when you make it executable, you'll just need to run “numbers.py” in the terminal to run the file. To make a file executable, you can use the command “chmod +x numbers.py” in this case. You can use “chmod 755 numbers.py” to give it root permissions or “sudo chmod +x numbers.py” for root executable. Here is some more information about the chmod command.</li>
</ul>
 

 
<ul>
 <li style="text-align: justify;">hostname — Use hostname to know your name in your host or network. Basically, it displays your hostname and IP address. Just typing “hostname” gives the output. Typing in “hostname -I” gives you your IP address in your network.</li>
</ul>
 

 
<ul>
 <li style="text-align: justify;">ping — Use ping to check your connection to a server. Wikipedia says, "Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network". Simply, when you type in, for example, “ping google.com”, it checks if it can connect to the server and come back. It measures this round-trip time and gives you the details about it. The use of this command for simple users like us is to check your internet connection. If it pings the Google server (in this case), you can confirm that your internet connection is active!</li>
</ul>
 

 
 
Tips and Tricks for Using Linux Command Line
 
<ul>
 <li style="text-align: justify;">You can use the clear command to clear the terminal if it gets filled up with too many commands.</li>
 <li style="text-align: justify;">TAB can be used to fill up in terminal. For example, You just need to type “cd Doc” and then TAB and the terminal fills the rest up and makes it “cd Documents”.</li>
 <li style="text-align: justify;">Ctrl+C can be used to stop any command in terminal safely. If it doesn't stop with that, then Ctrl+Z can be used to force stop it.</li>
 <li style="text-align: justify;">You can exit from the terminal by using the exit command.</li>
 <li style="text-align: justify;">You can power off or reboot the computer by using the command sudo halt and sudo reboot</li>
</ul>
 
 
 
<blockquote style="text-align: justify;">Useful Links: <a href="https://www.pluralsight.com/guides/beginner-linux-navigation-manual" target="_blank">Linux for beginners article/eng</a> <a href="https://www.guru99.com/unix-linux-tutorial.html" target="_blank">Linux for beginners article/eng</a> <a href="https://habr.com/ru/post/481398/" target="_blank">Linux commands article/rus</a> <a href="https://www.youtube.com/watch?v=IVquJh3DXUA" target="_blank">Linux for beginners video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=qwopGsaNF_Q" target="_blank">Linux for beginners video tutorial/rus</a></blockquote>

Linux

<h3>Git</h3> Installing, configuring, creating a repository For example, you need to transfer the information you created (from your home or work computer) to a server (for example, the GitHub repository). So that every member of your team, or, for example, an instructor, can access your files. In this case, you need to decide which folder or file you want to synchronize with the server, i.e. create a local storage (repository). We will consider it using the example of working with IDEA and managing from the console. This example is not specifically tied to the software used, so you can repeat this example for your specific situation. Step by step: <ol><li style="text-align: justify;">Create your own GIT HUB repository. This will be our server storage, which any participant can work with and access to it.</li><li style="text-align: justify;">Create your own free repository on GITHUB Install GIT itself, to do this, follow the link and download the current version for today: DOWNLOAD GIT Free</li><li style="text-align: justify;">In the appeared GIT console window on your computer (or cmd console), enter the following commands from the keyboard (each command ends by pressing the Enter key) :</li></ol> <ul><li style="text-align: justify;">git - this command displays a list of available commands, but for us now it simply serves as a confirmation that step 2 was done correctly and GIT is working</li><li style="text-align: justify;">git config --global user.name "Ivan Ivanov" - specify your name.</li><li style="text-align: justify;">git config --global user.email IvanIvanov@example.com - specify your email address</li><li style="text-align: justify;">cd: C: / Users / Ivanov / IdeaProjects / Project1 - with this command you go to the folder you need, which in the next step you will make as a local storage (i.e. this is your working directory where all project changes will be stored)</li><li style="text-align: justify;">git init - Create a repository in the current directory</li><li style="text-align: justify;">git add. - this command indexes (checks and remembers) all files (dot at the end of the command), which later will be subject to commit (essentially saved).</li><li style="text-align: justify;">git commit -m "Commit Text" - saving changes to a local folder.</li></ul> That's it, the local repository has been created, now we need to link the local and remote (GITHUB created in point 1) repositories. To do this, we need to enter the following commands: <ul><li style="text-align: justify;">git remote add origin https://github.com/GithubUser/RepositiryName.git - where, https://github.com/GithubUser/RepositiryName.git the address of the repository you created on GitHub can be copied directly from the browser with the addition of .git</li><li style="text-align: justify;">git push -u origin master</li></ul> Congratulations, you have linked the remote and local repositories. To upload files to the remote repository, run the command: git push - after pressing Enter, the first time you are asked to enter your GitHub username and password. You can now see the changes made on the GitHub site. Please note that after you have made changes with the files, in our example, this saved the project in IDEA, you need to run the following commands: <ul><li style="text-align: justify;">git add. - this command indexes (checks and remembers) all files (dot at the end of the command), which later will be subject to commit (essentially saved).</li><li style="text-align: justify;">git commit -m "Commit Text" - saving changes to a local folder.</li></ul> To transfer to the remote repository, run this command as well: git push In order, on the contrary, to get information from the remote repository to the local repository, run the command: git pull <blockquote style="text-align: justify;">Useful Links: <a href="https://www.atlassian.com/git/tutorials/what-is-git" target="_blank">Git article/eng</a> <a href="https://www.atlassian.com/git" target="_blank">Git article/eng</a> <a href="https://www.youtube.com/watch?v=SWYqp7iY_Tc" target="_blank">GitHub video tutorial/eng</a> <a href="https://www.youtube.com/watch?v=CRlGDDprdOQ" target="_blank">Git video tutorial/eng</a></blockquote>

Nothing makes the product more attractive but quality. We are here to provide high-quality of your software.

TESVAN A COMPANY OF QUALITY

Tesvan has taken over the testing of multiple projects from different business industries.  Below we have our projects categorized per industry. 