The latest articles on DEV Community by Sh Shipon (@sh_shipon_6676817e17728b1). https://dev.to/sh_shipon_6676817e17728b1 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2679965%2Fa02af8c7-b160-44f0-bf33-9d72fa435f51.png https://dev.to/sh_shipon_6676817e17728b1 en Sh Shipon Thu, 09 Jan 2025 10:38:10 +0000 https://dev.to/sh_shipon_6676817e17728b1/disadvantages-of-the-single-responsibility-principlesrp-39oc https://dev.to/sh_shipon_6676817e17728b1/disadvantages-of-the-single-responsibility-principlesrp-39oc <div class="ltag__link"> <a href="/nozibul_islam_113b1d5334f" class="ltag__link__link"> <div class="ltag__link__pic"> <img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1971849%2Fe97063c6-1893-40f0-af60-b650acae49cd.png" alt="nozibul_islam_113b1d5334f"> </div> </a> <a href="https://dev.to/nozibul_islam_113b1d5334f/disadvantages-of-the-single-responsibility-principlesrp-ihm" class="ltag__link__link"> <div class="ltag__link__content"> <h2>Disadvantages of the Single Responsibility Principle(SRP)</h2> <h3>Nozibul Islam ・ Sep 28 '24</h3> <div class="ltag__link__taglist"> <span class="ltag__link__tag">#solidprinciples</span> <span class="ltag__link__tag">#java</span> <span class="ltag__link__tag">#javascript</span> <span class="ltag__link__tag">#softwareengineering</span> </div> </div> </a> </div> oop designpatterns solidprinciples Sh Shipon Thu, 09 Jan 2025 10:17:28 +0000 https://dev.to/sh_shipon_6676817e17728b1/test-case-vs-test-scenario-3cnl https://dev.to/sh_shipon_6676817e17728b1/test-case-vs-test-scenario-3cnl <h3> Test Scenario Vs Test Case. </h3> <h4> Test Scenario </h4> <ul> <li> <strong>Definition:</strong> A high-level description or outline of what needs to be tested. It focuses on the functionality or workflow to be validated, not the specific steps.</li> <li> <strong>Detail Level:</strong> Less detailed and broader in scope. It represents a concept or a situation that needs testing, typically at a more abstract level.</li> <li> <strong>Purpose:</strong> Used to ensure comprehensive coverage of the application and to identify all the possible areas that need testing.</li> </ul> <h4> Focus </h4> <p>Focuses on what to test (e.g., user login process, fund transfer workflow).</p> <h4> Example: </h4> <ul> <li>"Test the login functionality."</li> <li>"Test fund transfer between accounts."</li> </ul> <h4> When Used </h4> <p>Primarily used during the initial stages of testing to outline the general areas to be covered.</p> <h4> Test Case </h4> <ul> <li> <strong>Definition:</strong> A detailed set of specific instructions or steps to execute a test, which includes inputs, actions, expected outcomes, and actual results.</li> <li> <strong>Detail Level:</strong> Highly detailed and specific. Each test case outlines how the test should be performed and provides step-by-step guidance.</li> <li> <strong>Purpose:</strong> Used to ensure specific aspects of the application behave as expected under certain conditions.</li> </ul> <h4> Focus </h4> <p>Focuses on how to test the scenario, including precise steps, expected results, and test data.</p> <h4> Example: </h4> <h5> <strong>Test Case for Login:</strong> </h5> <ol> <li>Step 1: Open the login page.</li> <li>Step 2: Enter a valid username and password.</li> <li>Step 3: Click the login button.</li> </ol> <blockquote> <p><strong>Expected Result:</strong> The user is redirected to the dashboard.</p> </blockquote> <h4> When Used </h4> <p>Used during the execution phase to ensure specific functionality is working as intended, step by step.</p> webdev qa testing