mfaisalkhatri

Criteria	Smoke Testing	Regression testing
Goal	The goal of smoke testing is to uncover the critical or blocker issues in the application using the test cases that cover important functionalities of the software.	The goal of regression testing is to ensure that the new code changes does not break the existing functionality of the software.
Scope	Smoke testing verifies the stability of the software by testing critical user journeys of the software.	Regression testing covers overall software features to verify if everything is working as expected.
When Performed?	Smoke testing should be performed after a new build is released after major code changes.	Regression testing is performed after a new feature is added to the software or major rework is done.
Test Cases Used	Test Cases related to critical functionalities of the software are used in

mfaisalkhatri

Criteria	Regression Testing	Retesting
Goal	The goal of regression testing is to make sure that the new code changes does not break the existing functionality of the software.	The goal of retesting is to make sure that the reported bug has been fixed after code changes.
Scope	Regression testing covers overall software or critical features of the software to check if everything is working as expected.	Retesting covers only the specific failed test case or scenario.
When Performed?	Regression testing is performed after a new feature is added to the software or major rework is done.	Retesting is performed after the failed test cases are fixed.
Test Cases	Regression testing considers the passed as well as failed test cases to check the overall stability of the software.	Retesting covers only the specific failed test cases/scenarios.
Example	Adding new option to si

mfaisalkhatri

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite name="Sauce Demo Website Tests" parallel="tests" thread-count="4" verbose="2">
    <test name="selenium 4 Tests with Chrome Browser">
        <parameter name="browser" value="chrome"/>
        <classes>
            <class name="io.github.mfaisalkhatri.tests.saucedemo.SauceDemoTests">
                <methods>
                    <include name="loginSauceDemoTest"/>
                    <include name="logOutSauceDemoTest"/>

adojos

Maven Commands Reference

Maven offers a good set of commands and CLI Options to carry out wide range of Dev tasks. Most of these commands are in fact Maven build life cycles, phases and goals.

Here is a list of common Maven commands along with explanation. But before we go through the Maven commands, it is good idea to understand the structure or syntax of Maven commands along with a brief about the Maven lifecycle, phases and goals.

Maven Commands Syntax

WebRTCGame

Useful Links

MDN JavaScript

23 Free JavaScript Books

A curated collection of awesome & free JavaScript books to help you learn the JavaScript programming language.

If you know of any other free JavaScript books that you think should be on this list, please let me know in the comments section and I will get them added.

lukas-h

Markdown License badges

Collection of License badges for your Project's README file.
This list includes the most common open source and open data licenses.
Easily copy and paste the code under the badges into your Markdown files.

Notes

• The badges do not fully replace the license informations for your projects, they are only emblems for the README, that the user can see the License at first glance.

Translations: (No guarantee that the translations are up-to-date)

• 🇫🇷 Cette liste en français