<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Soundharapandiyan B</title>
    <description>The latest articles on DEV Community by Soundharapandiyan B (@soundhar).</description>
    <link>https://dev.to/soundhar</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1162635%2F8b120c8b-2df7-40c7-8bb9-65a1f70f4e49.jpg</url>
      <title>DEV Community: Soundharapandiyan B</title>
      <link>https://dev.to/soundhar</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/soundhar"/>
    <language>en</language>
    <item>
      <title>Task 4</title>
      <dc:creator>Soundharapandiyan B</dc:creator>
      <pubDate>Sat, 14 Oct 2023 01:52:42 +0000</pubDate>
      <link>https://dev.to/soundhar/task-4-51lg</link>
      <guid>https://dev.to/soundhar/task-4-51lg</guid>
      <description>&lt;p&gt;Manual testing is a software testing technique in which a human tester, without the use of automation tools or scripts, executes test cases to identify defects or issues in a software application. In manual testing, the tester acts as an end user and interacts with the application's user interface, providing inputs and checking the outputs to ensure that the software behaves as expected.&lt;/p&gt;

&lt;p&gt;Manual testing offers several benefits and drawbacks, and the choice between manual and automated testing depends on the specific context and testing requirements. &lt;/p&gt;

&lt;p&gt;Benefits of Manual Testing:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Human Judgment: Manual testers can apply their critical thinking and domain knowledge to uncover subtle defects that automated tests might miss. They can identify issues related to usability, user experience, and other qualitative aspects.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Exploratory Testing: Manual testers excel at exploratory testing, where they actively explore the software to find unexpected issues, making it valuable for uncovering new defects.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Adaptability: Manual testing is flexible and adaptable to changes in the software, making it suitable for dynamic or rapidly evolving projects.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Cost-Effective for Small Projects: For small-scale projects or projects with a limited budget, manual testing may be more cost-effective than setting up and maintaining automated testing infrastructure.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Early Testing: Manual testing can begin even before a user interface is fully developed, allowing early testing of requirements and design.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Drawbacks of Manual Testing:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Resource-Intensive: Manual testing can be time-consuming and costly, especially for large or complex applications. It requires skilled testers who need time to execute test cases manually.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Repetitive Tasks: Testers may become fatigued when repeatedly executing the same test cases, leading to oversight and reduced accuracy.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Limited Test Coverage: Manual testing might not cover all possible test scenarios, leading to gaps in test coverage. Automated tests can provide more comprehensive coverage.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Not Suitable for Regression Testing: Regression testing, which involves repeatedly testing existing functionalities after each code change, can be inefficient and error-prone when done manually. Automated tests are better suited for this task.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Not Scalable: As the application grows in complexity, manual testing becomes less scalable, and the time required for testing increases.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

</description>
    </item>
    <item>
      <title>Task 3</title>
      <dc:creator>Soundharapandiyan B</dc:creator>
      <pubDate>Sat, 14 Oct 2023 01:39:30 +0000</pubDate>
      <link>https://dev.to/soundhar/task-3-1p30</link>
      <guid>https://dev.to/soundhar/task-3-1p30</guid>
      <description>&lt;p&gt;Functional testing and non-functional testing are two types of software testing. The difference between them are:&lt;/p&gt;

&lt;p&gt;Functional Testing:&lt;br&gt;
        This type of testing focuses on verifying that the software functions according to its specified requirements. It checks whether the application performs its intended functions correctly. It mainly deals with the "what" aspect of the software.&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;     It primarily involves testing the features and functionalities of the software. This includes testing individual functions, user interfaces, data processing, and interactions between different parts of the software.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;Non-Functional Testing:&lt;br&gt;
          Non-functional testing, on the other hand, assesses the qualities or characteristics of the software, such as performance, reliability, usability, and scalability. It evaluates how well the software performs its functions under various conditions and measures attributes like speed, security, and user-friendliness. Non-functional testing deals with the "how" aspect of the software.&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;     It covers a broader range of attributes and characteristics beyond the core functionality. Non-functional testing includes areas like load testing, security testing, usability testing, and performance testing.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;In summary, functional testing focuses on verifying that the software's features work as intended, while non-functional testing assesses various quality attributes like performance, security, and usability. Both types of testing are essential to ensure a software application meets its functional requirements and provides a satisfactory user experience.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Task 2</title>
      <dc:creator>Soundharapandiyan B</dc:creator>
      <pubDate>Mon, 18 Sep 2023 04:44:47 +0000</pubDate>
      <link>https://dev.to/soundhar/task-2-1ai2</link>
      <guid>https://dev.to/soundhar/task-2-1ai2</guid>
      <description>&lt;p&gt;Boundary value Analysis:&lt;br&gt;
          Boundary value Analysis is Testing the software at the boundaries of input values to identify any defects or errors at the boundaries of input values.&lt;/p&gt;

&lt;p&gt;Some examples of Boundary value Analysis:&lt;/p&gt;

&lt;p&gt;Input values between 1 and 100&lt;br&gt;
     Valid inputs are above 1 and below 100.&lt;br&gt;
     Invalid inputs are below 2 and above 99.&lt;/p&gt;

&lt;p&gt;Decision Table Testing:&lt;br&gt;
         Decision Table Testing is the testing technique used to test combinations of conditions or rules systematically. For the purpose of ensure that the application behaves correctly or not for various combinations of inputs.&lt;/p&gt;

&lt;p&gt;Some example for Decision Table Testing:&lt;/p&gt;

&lt;p&gt;Condition 1: Age&lt;br&gt;
A1: Under 18&lt;br&gt;
A2: 18 to 65&lt;br&gt;
A3: Above 65&lt;/p&gt;

&lt;p&gt;Condition 2: Membership Status&lt;br&gt;
M1: Not a Member&lt;br&gt;
M2: Standard Member&lt;br&gt;
M3: Premium Member&lt;/p&gt;

&lt;p&gt;Rule 1 - If A1 and M1 means not eligible.&lt;br&gt;
Rule 2 - If A1 and M2 means not eligible.&lt;br&gt;
Rule 3 - If A1 and M3 means not eligible.&lt;br&gt;
Rule 4 - If A2 and M1 means not eligible.&lt;br&gt;
Rule 5 - If A2 and M2 means eligible for 5% of discount.&lt;br&gt;
Rule 6 - If A2 and M3 means eligible for 25% of discount.&lt;br&gt;
Rule 7 - If A3 and M1 means not eligible.&lt;br&gt;
Rule 8 - If A3 and M2 means eligible for 20% of discount.&lt;br&gt;
Rule 9 - If A3 and M3 means eligible for 40% of discount.&lt;/p&gt;

&lt;p&gt;In this Decision Table Testing, we have identified all possible conditions of combinations.&lt;/p&gt;

&lt;p&gt;Use Case Testing:&lt;br&gt;
         Use Case Testing is a technique that focuses on testing the functionality of a software application based on its use cases. Use cases represent real-world scenarios or interactions between users and the system. &lt;/p&gt;

&lt;p&gt;LCSAJ (Linear Code Sequence and Jump) Testing:&lt;br&gt;
           LCSAJ Testing is a structural testing technique that focuses on testing different linear code sequences and possible jumps within a program. It helps ensure that every executable statement in the code is tested at least once.&lt;/p&gt;

&lt;p&gt;LCSAJ Testing helps identify issues related to control flow and logic within a program.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Task 1</title>
      <dc:creator>Soundharapandiyan B</dc:creator>
      <pubDate>Sat, 16 Sep 2023 09:20:11 +0000</pubDate>
      <link>https://dev.to/soundhar/task-1-1d55</link>
      <guid>https://dev.to/soundhar/task-1-1d55</guid>
      <description>&lt;p&gt;What is Software Testing?&lt;/p&gt;

&lt;p&gt;Software Testing is the process that evaluating that the software or product or application what dose supposed to do. Testing reduce bugs, reduce development costs. Testing will improve the performance of software or product or application. Software testing is to ensure that software or product or application functions correctly, attains requirements of client, and deliver a quality software or product or application to client. &lt;/p&gt;

&lt;p&gt;What we need to know about Software Testing?&lt;/p&gt;

&lt;p&gt;Software Testing means running multiple tests. To improve the performance of software or product or application. There are various types of software testing (Manual testing, Automated testing, Regression testing, User Acceptance Testing). It is important to testing the software or product or application for the purpose of Quality assurance, User satisfaction, Security, etc.,&lt;/p&gt;

&lt;p&gt;What is the relevance of Software Testing?&lt;/p&gt;

&lt;p&gt;Software Testing will identify defects, reduce bugs, and increase quality of software or product or application. Software Testing is necessary to find the mistakes, and helps us to identify bugs or errors early, so that we can be fix mistakes, bugs or errors before the product was delivered to the client.&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
