<?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: Rasmitha B</title>
    <description>The latest articles on DEV Community by Rasmitha B (@rasmitha_b_).</description>
    <link>https://dev.to/rasmitha_b_</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%2F3844380%2Fa262517e-5b91-4e26-9514-ff122a252b1a.png</url>
      <title>DEV Community: Rasmitha B</title>
      <link>https://dev.to/rasmitha_b_</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/rasmitha_b_"/>
    <language>en</language>
    <item>
      <title>Boundary value analysis(BVA)</title>
      <dc:creator>Rasmitha B</dc:creator>
      <pubDate>Fri, 27 Mar 2026 10:33:56 +0000</pubDate>
      <link>https://dev.to/rasmitha_b_/boundary-value-analysisbva-59dj</link>
      <guid>https://dev.to/rasmitha_b_/boundary-value-analysisbva-59dj</guid>
      <description>&lt;p&gt;BVA means testing the edges of Input ranges.&lt;br&gt;
When the application allows values only within a Range, We do not test the all values .We do test the smallest value ,biggest value and values just near them because mistakes usually occurs at the edges.&lt;br&gt;
Because most software bugs happens at minimum ,Maximum and around the edges&lt;br&gt;
EX: Age must be 10 to 40&lt;/p&gt;

&lt;p&gt;we usually test 9,10,11,39,40 and 41 values&lt;/p&gt;

&lt;p&gt;we accept 10,11,39 and 40 value&lt;br&gt;
we do not accept 9 and 41&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Common Manual testing techniques</title>
      <dc:creator>Rasmitha B</dc:creator>
      <pubDate>Thu, 26 Mar 2026 11:02:24 +0000</pubDate>
      <link>https://dev.to/rasmitha_b_/common-manual-testing-techniques-1bc7</link>
      <guid>https://dev.to/rasmitha_b_/common-manual-testing-techniques-1bc7</guid>
      <description>&lt;p&gt;&lt;strong&gt;1.Smoke testing:&lt;/strong&gt;&lt;br&gt;
Smoke testing is basically performed before actual test begins .Smoke testing means quick test performed on critical or high level functionality of the new build.&lt;br&gt;
EX: Login page, Navigation ,Credential testing&lt;br&gt;
&lt;strong&gt;2.Sanity testing:&lt;/strong&gt;&lt;br&gt;
Sanity test will be done when small fixes or changes done in new build .To ensure that new fixes or changes working as expected.&lt;br&gt;
ex: Add product to cart, Apply coupon&lt;br&gt;
&lt;strong&gt;3.Regression testing:&lt;/strong&gt;&lt;br&gt;
Regression test will be done when new feature added(fixes or update the code) to application .To test to ensure the existing version of functionality is working fine.&lt;br&gt;
&lt;strong&gt;4.Whitebox testing:&lt;/strong&gt; &lt;br&gt;
White Box testing usually done with the help of developers .To test internal structure of the code we call it as Whitebox testing . Technical knowledge required to test this.&lt;br&gt;
&lt;strong&gt;5. Block box testing:&lt;/strong&gt;&lt;br&gt;
Block box testing done by Testers. This technique not required technical knowledge. Product knowledge (Requirements)is enough to test.&lt;br&gt;
&lt;strong&gt;6.Monkey testing:&lt;/strong&gt; &lt;br&gt;
Monkey testing is Software testing technique in which application test Randomly or unstructured testing .&lt;br&gt;
&lt;strong&gt;7.End to End testing :&lt;/strong&gt;&lt;br&gt;
It is the method where we test entire application flow from start to end ,Just like a real user .It covers and verifies all integrated components work together &lt;br&gt;
correctly.&lt;br&gt;
&lt;strong&gt;8.Retesting:&lt;/strong&gt;&lt;br&gt;
It is focus only on Failed test cases ,To test specific test cases are working as expected or not. Not whole application.&lt;/p&gt;

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