<?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: Gayathri</title>
    <description>The latest articles on DEV Community by Gayathri (@pgayathri).</description>
    <link>https://dev.to/pgayathri</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1285663%2F81105584-a573-4aae-a33c-780094946a4c.png</url>
      <title>DEV Community: Gayathri</title>
      <link>https://dev.to/pgayathri</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/pgayathri"/>
    <language>en</language>
    <item>
      <title>Task4</title>
      <dc:creator>Gayathri</dc:creator>
      <pubDate>Thu, 29 Feb 2024 05:37:19 +0000</pubDate>
      <link>https://dev.to/pgayathri/task4-1p7a</link>
      <guid>https://dev.to/pgayathri/task4-1p7a</guid>
      <description>&lt;p&gt;Manual testing is testing the software manually all functionality and quality are as per the requirements . &lt;br&gt;
Testing is based on &lt;br&gt;
1.Human intelligence&lt;br&gt;
2.No use of automation tools are used.&lt;br&gt;
3.Each and every functionality is validated manually by the tester.&lt;br&gt;
4.Testing is based on the experience of the project.&lt;br&gt;
5.Manual testing helps to find issue which cannot be find by automation tool.&lt;/p&gt;

&lt;p&gt;Disadvantage&lt;br&gt;
1.Manual testing is time consuming .&lt;br&gt;
2.Doing regression is hectic.&lt;br&gt;
3.Human errors can occur. &lt;/p&gt;

</description>
    </item>
    <item>
      <title>Task3</title>
      <dc:creator>Gayathri</dc:creator>
      <pubDate>Thu, 29 Feb 2024 05:27:34 +0000</pubDate>
      <link>https://dev.to/pgayathri/task3-gpp</link>
      <guid>https://dev.to/pgayathri/task3-gpp</guid>
      <description>&lt;p&gt;Functional testing : Functional testing is done to test the functionality of the software are as per expected(Requirements) without any bugs.&lt;br&gt;
 Functional testing includes smoke testing,sanity testing,Integration testing,system testing,User acceptance testing.&lt;/p&gt;

&lt;p&gt;Example: Smoke testing is done when a build is ready for testing which verifies the critical functionality is working and ready to proceed with testing or not ?&lt;/p&gt;

&lt;p&gt;Non functionality testing : This testing is done to test the non functionality like the software performance,usability,compatibility and accessibility .&lt;/p&gt;

&lt;p&gt;For example : Performance testing is done to test the performance of the system under heavy load or traffic in the application .&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Task2</title>
      <dc:creator>Gayathri</dc:creator>
      <pubDate>Tue, 20 Feb 2024 05:36:01 +0000</pubDate>
      <link>https://dev.to/pgayathri/task2-449f</link>
      <guid>https://dev.to/pgayathri/task2-449f</guid>
      <description>&lt;p&gt;&lt;strong&gt;Boundary value analysis&lt;/strong&gt;-Boundary value analysis is testing the boundary values( example :Range 0 to 10) For example if the user is allowed to enter only till 10 in a input text box then the testing will inculde validating the boundary values like 0 which is the minimum value and maximum value as 10 .The boundary value  will be 1 and 9 . &lt;br&gt;
The testing will validate invalid value-11 and negative value  -1 &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Decision table testing&lt;/strong&gt; : Here the testcases are designed with  input combinations and validating results based on the combinations.&lt;br&gt;
For example: Consider Login and Password&lt;br&gt;
Login :           P    F    P    F&lt;br&gt;
Password:         F    P    F    F&lt;br&gt;
Expected Result: Success  Fail Fail Fail&lt;/p&gt;

&lt;p&gt;So here the login is successful only when login and password is entered correctly and we have checked different conditions .&lt;/p&gt;

&lt;p&gt;Use case testing : Use case testing means validating the entire e2e functionality of a build .It includes all the scenarios which will assure the quality and bug free product .&lt;/p&gt;

&lt;p&gt;LCSAJ testing : Linear code sequence and jump which means testing the code .&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Task1</title>
      <dc:creator>Gayathri</dc:creator>
      <pubDate>Tue, 20 Feb 2024 05:05:42 +0000</pubDate>
      <link>https://dev.to/pgayathri/task1-gb0</link>
      <guid>https://dev.to/pgayathri/task1-gb0</guid>
      <description>&lt;p&gt;Software testing is testing whether the product built is as right and as expected .It is nothing but validating/verification of  the software application . &lt;br&gt;
The testing will ensure the quality of the product and to avoid  major issues to the end user which is very important because atlast it's the trust/money of the customer .&lt;/p&gt;

&lt;p&gt;For example if we consider baking application.if we software testing is not done correctly there are chances in loosing the trust of the bank and money and customer data which is very private .&lt;/p&gt;

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