<?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: renuga devaraj</title>
    <description>The latest articles on DEV Community by renuga devaraj (@renuga_devaraj_656b15ba3e).</description>
    <link>https://dev.to/renuga_devaraj_656b15ba3e</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%2F3800222%2F6eb1b23a-d361-4eaf-a124-605c66322e9c.jpg</url>
      <title>DEV Community: renuga devaraj</title>
      <link>https://dev.to/renuga_devaraj_656b15ba3e</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/renuga_devaraj_656b15ba3e"/>
    <language>en</language>
    <item>
      <title>Software Testing Technique</title>
      <dc:creator>renuga devaraj</dc:creator>
      <pubDate>Tue, 03 Mar 2026 05:36:36 +0000</pubDate>
      <link>https://dev.to/renuga_devaraj_656b15ba3e/software-testing-technique-109</link>
      <guid>https://dev.to/renuga_devaraj_656b15ba3e/software-testing-technique-109</guid>
      <description>&lt;p&gt;&lt;strong&gt;1. COMMON MANUAL TESTING TECHNIQUES&lt;/strong&gt;&lt;br&gt;
Manual Testing is a process in software development where testers execute test cases manually  without using any automation tools. &lt;br&gt;
There are several types of Manual Testing &lt;br&gt;
1.Black Box Testing - Test the software functionality without the knowledge of internal code structure. Testers only focus on inputs and expected outputs without considering the internal workings of system.&lt;br&gt;
2.White Box Testing - Test the software functionality and knowledge of code. Usually it  performed by developers.&lt;br&gt;
3.Grey Box Testing - Grey-box testing combines both black-box and white-box testing. Testers have partial knowledge of the internal code and structure. Testers create test cases focusing on inputs, outputs, and internal processes.&lt;br&gt;
4.Exploratory Testing –Without following a specific test plan, testers can freely test the software.&lt;br&gt;
 5.Usability Testing - It tests the software to evaluate whether its user-friendliness and ease of use.&lt;br&gt;
6.Ad-hoc Testing - The goal is to break the application by trying random inputs, actions, or workflows.&lt;br&gt;
7.Functional Testing – Verifies the software performs function correctly according to business requirements.&lt;br&gt;
8.Regression Testing - Regression testing ensures that new changes, such as code modifications, bug fixes, or any feature additions that do not impact the existing functionalities.&lt;br&gt;
9.Acceptance Testing (UAT) - Test the software to determine if it meets the business requirements and expectations.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Boundary value testing – It tests the software at the boundaries of input values to identify any defects.&lt;/li&gt;
&lt;li&gt;Security Testing: This testing will focuses on finding security issues in the code.&lt;/li&gt;
&lt;li&gt;End-to-End (E2E) Testing: Validates the entire application workflow from start to finish, simulating real-world user scenarios&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;strong&gt;2.Boundary Value Analysis&lt;/strong&gt;&lt;br&gt;
• Boundary Value Analysis(BVA) is a software &lt;/p&gt;

&lt;p&gt;testing technique used to verify system behavior at the edges or boundaries of input values. &lt;br&gt;
• Every partition have maximum and minimum values and these maximum and minimum values are the boundary values of a partition. &lt;br&gt;
• By doing this BVA testing technique it will get broke so it is important to do before the deployment of code.&lt;br&gt;
Valid Boundary Value     - A boundary value for valid Partition &lt;br&gt;
Invalid Boundary Value  - A boundary value for invalid Partition&lt;br&gt;
For each variable we have to check :&lt;br&gt;
• Minimum value&lt;br&gt;
• Above Minimum Value&lt;br&gt;
• Nominal value&lt;br&gt;
• Maximum value&lt;br&gt;
• Below maximum value&lt;br&gt;
Example for BVA technique:&lt;br&gt;
Consider Numbers from 10 to 20&lt;/p&gt;

&lt;p&gt;Minimum - 1 Min,Min+1,Nominal,Max-1,Max Maximum+1&lt;br&gt;
9                   10,11,15,19,20             21&lt;/p&gt;

&lt;p&gt;Valid Test Value : 10,11,15,19,20&lt;br&gt;
Invalid test Value : 9,21&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.Desicion Table Testing&lt;/strong&gt;&lt;br&gt;
     Decision table testing is a system testing technique that uses decisions tables to design and execute the test cases and this creating decisions tables that capture various of input condition and corresponding actions or outcomes. &lt;br&gt;
     It helps the testers to analyze these decisions tables to derive the test case that cover different scenario based on the condition.&lt;br&gt;
Parts of decision table:&lt;br&gt;
1.Condition Stubs : &lt;br&gt;
      It is used to identify the particular action or a set of actions.&lt;br&gt;
2.Action :&lt;br&gt;
       All possible conditions are given below the Condition stub.&lt;br&gt;
3.Condition Entries :&lt;br&gt;
 In Condition entries part of table, there are multiple rows and columns called Rule&lt;br&gt;
4.Action Entries : &lt;br&gt;
In Action entry, every entry has some action or set of action which is given in lower right portion of the table called Outputs.&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;  Stubs         Entries

       C1
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;Condition C2&lt;br&gt;
           C3&lt;br&gt;&lt;br&gt;
           A1&lt;br&gt;
  Action   A2&lt;br&gt;
           A3&lt;br&gt;
           A4   &lt;/p&gt;

&lt;p&gt;Example : A payment processing system needs to decide whether to complete or decline a transaction based on validity of credit card.&lt;br&gt;
Condition Stub:       Rule 1    Rule 2   Rule 3&lt;br&gt;
Credit Card Valid   Yes No     Yes&lt;br&gt;
Payment Processed   Yes Yes    No&lt;br&gt;
Action Stub:&lt;br&gt;&lt;br&gt;
Complete Transaction    X           X&lt;br&gt;
Decline Transaction      Impossible &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. FUTURE OF MANUAL TESTING USING AI&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;• AI tools with Manual testing, we can create testing process       faster, more reliable and delivers high quality software.&lt;br&gt;
• It provides more accurate results and saves time. &lt;br&gt;
• AI tools are revolutionizing four main functions of software testing like test case preparation, test data generation, predicting defects and analyzing results.&lt;/p&gt;

&lt;p&gt;1.Test Case Preparation&lt;br&gt;
AI can interpret natural language descriptions using NLP (Natural Language Processing) of testcases and it can automatically translate them into executable test scripts.&lt;br&gt;
2.Test Data generation&lt;br&gt;
AI can create test data that closely resembles real user inputs enhancing the quality of testing.&lt;br&gt;
3.Test Execution&lt;br&gt;
It can facilitate parallel execution across multiple environments, reducing execution time. It eliminates repetitive tests.&lt;br&gt;
4.Debugging&lt;br&gt;
AI can easily identify unusual patterns in application and helps the tester to find potential issues and bugs. &lt;br&gt;
It can also help tester to identify areas where defects are more likely to occur.&lt;br&gt;
It can also analyze system logs to identify the root cause of the defects.&lt;/p&gt;

</description>
      <category>beginners</category>
      <category>softwareengineering</category>
      <category>testing</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
