The Study Secretz

  Yes...!! you heard is right 😊and it’s possible with simple coded steps. When we’re getting into a Daily work, we’ve to deal with many Tools, Editors, Folders and Files. Opening of all these on daily basis is a tedious job 😖. In My Scenario, daily I’ve to open multiple chrome browsers, project folders, files and visual studio to continue my regular project tasks. To mitigate this, I am bringing up this article for you Just by writing simple coded steps in a Notepad/any editor to overcome this. Write below code in notepad and click on File->Save As -> Give your name followed by .bat  extension and click on OK button. Now your shortcut key is ready. Just double click it and have fun with it. Below is the code: @echo off :: Open folders start %USERPROFILE%\Documents\ start %USERPROFILE%\Desktop\Test\ :: Open files start "" "%USERPROFILE%\Desktop\DeskTop\SM\test.txt" ::Open browser start chrome.exe start " " https://www.freecodecamp.org/learn...

Severity vs Priority

Test Plan : It is high level document which explains Test Strategy, Time Lines and Available resources in detail. This document contains, Ø    Objective Ø    Test Strategy Ø    Resources Ø    Entry Criteria Ø    Exit Criteria Ø    Use/Test Cases Ø    Tasks Ø    Features to be Tested/Not Tested Ø    Risks/Assumption

Difference between Re-testing and Regression testing: Re-Testing: When tester finds the bug and report to developers and developer fix that bug now if tester tests only that test case in which he found the bug with same or different data then it is known as retesting. Re testing requires re-running of the failed test cases. Re testing is plan based for bug fixes in build notes and docs. Regression Testing: After modification or fixing the bug if tester test that test case in which he found the bug and test all the or specified test cases which he executes earlier then it is known as regression testing . The aim of this testing is that bug fixing is not affect the passed test cases.     It is an important activity, performed on modified software to provide confidence that changes are correct and do not affect the other functionality and components.   Regression testing is generic and may not be always specific to defect fixes.