<?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: karthicks</title>
    <description>The latest articles on DEV Community by karthicks (@karthi27).</description>
    <link>https://dev.to/karthi27</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%2F1265331%2F42333fbe-9d29-44be-a229-ee0325a30f31.png</url>
      <title>DEV Community: karthicks</title>
      <link>https://dev.to/karthi27</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/karthi27"/>
    <language>en</language>
    <item>
      <title>Task 2</title>
      <dc:creator>karthicks</dc:creator>
      <pubDate>Tue, 06 Feb 2024 00:55:44 +0000</pubDate>
      <link>https://dev.to/karthi27/task-2-107h</link>
      <guid>https://dev.to/karthi27/task-2-107h</guid>
      <description>&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;BOUNDARY VALUE ANALYSIS&lt;/strong&gt;&lt;br&gt;
It is the software testing technique in which tests are designed to include representatives of boundary values in a range. The idea comes from the boundary. Given that we have a set of test vectors to test the system, a topology can be defined on the set. It checks for the input values near the boundary that have a higher chance of error. Every partition has its maximum and minimum values are the boundary values of the partition&lt;br&gt;
Example:&lt;br&gt;
Need to set a minimum age requirement of 18 and maximum of 65. Need to provide the input values at the upper and lower limits along with the values which are inside or outside of the limit&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;DECISION TABLE TESTING&lt;/strong&gt;&lt;br&gt;
It is the software testing technique used to test the system behaviour for the different input combinations. This is a systematic approach where the different input combinations and their corresponding system behaviour are captured in a tabular form. It is a very effective tool used for both complex software testing and requirements management. A decision table testing helps to check the all possible combinations of conditions for testing and testers can easily identify missed conditions &lt;br&gt;
Example:&lt;br&gt;
Username and password both were wrong. The user is shown an error message&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;3.&lt;strong&gt;USE CASE TESTING&lt;/strong&gt;&lt;br&gt;
 It is generally a part of block box testing and helps developers and testers to identify test scenarios that exercise the whole system on each transition basis from start to finish. Business experts and developers must have a mutual understanding of the requirement. It is a functional testing technique that helps in identifying and testing scenarios on the whole system. It is used to develop the test cases at the system level or acceptance level&lt;br&gt;
Example:&lt;br&gt;
Online E-commerce purchase might include separate reports for adding item to the cart, selecting the payment  type and choosing a shipping  and delivery option&lt;br&gt;
4.&lt;strong&gt;LCSAJ TESTING&lt;/strong&gt;&lt;br&gt;
It stands for Linear Code Sequence and Jump. It is a white box testing methodology used to determine the code coverage, what percentage of the code is executed with the existing test cases. It helps in designing new test cases which can increase the coverage of the code under test. Once the code coverage reaches the certain level we can stop the testing&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Task-4</title>
      <dc:creator>karthicks</dc:creator>
      <pubDate>Sun, 04 Feb 2024 05:40:13 +0000</pubDate>
      <link>https://dev.to/karthi27/task-4-2kd1</link>
      <guid>https://dev.to/karthi27/task-4-2kd1</guid>
      <description>&lt;p&gt;Manual testing is the process of manually testing the software for defects. It requires a tester to to plat the role an end user where by they use most of the application's features to ensure correct behaviour. To guarantee completeness of testing, the tester often follows a written test plan that leads them through a set of important test cases. &lt;/p&gt;

&lt;p&gt;benefits:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Low cost operation and no software tools are used
*Most bugs are caught by manual testing
*Humans observe and judge better than the automated tools
drawbacks:
*It uses a comparatively large number of human resources
*It's costly in the short run
*it is very time consuming
*It does not cover the all aspects&lt;/li&gt;
&lt;/ul&gt;

</description>
    </item>
    <item>
      <title>Task-4</title>
      <dc:creator>karthicks</dc:creator>
      <pubDate>Sun, 28 Jan 2024 19:38:34 +0000</pubDate>
      <link>https://dev.to/karthi27/task-4-o5n</link>
      <guid>https://dev.to/karthi27/task-4-o5n</guid>
      <description>&lt;p&gt;Manual testing is a software testing process in which cases are executed manually without using any automated tool. All test cases executed by the tester manually according to the end users perspective. It ensures whether the application is working as mentioned in the requirement document or not. Test cases are planned and implemented to complete almost 100 percent of the software application. Test case reports are generated manually.&lt;br&gt;
Drawbacks:&lt;br&gt;
It uses a comparatively large number of human resources &lt;br&gt;
It is costly in the short run&lt;br&gt;
It is very timing consuming&lt;br&gt;
It does not cover all aspects of testing&lt;br&gt;
Benefits:&lt;br&gt;
If If you are using block box testing you don't need programming knowledge&lt;br&gt;
It is easy for new testers to learn&lt;br&gt;
The software end up 100 percent bug free&lt;br&gt;
It's cost effective&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Task 3</title>
      <dc:creator>karthicks</dc:creator>
      <pubDate>Sun, 28 Jan 2024 19:09:24 +0000</pubDate>
      <link>https://dev.to/karthi27/task-3-m0p</link>
      <guid>https://dev.to/karthi27/task-3-m0p</guid>
      <description>&lt;p&gt;*&lt;em&gt;Functional testing *&lt;/em&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;It verifies the operations and actions of the application
*It is based on the requirements of the customers
*it helps to enhance the behavior of the customers application
*Functional testing is easily to execute manually 
*It tests what the product does
*Functional testing is based on the business requirements
Examples:
Unit testing, Smoke testing, Integration testing, Regression testing&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Non-functional testing:&lt;br&gt;
*It verifies the behavior of the application&lt;br&gt;
*It is based on the expectations of the customers&lt;br&gt;
*It helps to improve the performance of the application&lt;br&gt;
*It is hard to execute non-functional testing manually&lt;br&gt;
*It describes hoe the product does&lt;br&gt;
*non-functional testing is based on the performance requirement&lt;br&gt;
Examples:&lt;br&gt;
performance testing, load testing, stress testing, scalability testing&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Task 1</title>
      <dc:creator>karthicks</dc:creator>
      <pubDate>Sat, 27 Jan 2024 10:05:06 +0000</pubDate>
      <link>https://dev.to/karthi27/task-1-589g</link>
      <guid>https://dev.to/karthi27/task-1-589g</guid>
      <description>&lt;p&gt;software testing is the way assess the quality of software and its reduce the risk of failure. Software testing is the process of test planning analysis, designing, implements and reports. Analysing the product requirements for the completeness and correctness in various contexts like industry perspective, business perspective, usability, performance, security. &lt;br&gt;
Reviewing the product architecture and the overall design of the product. Working with the product developers on improvement in the coding technique, design patterns, test can be written as part of code based on various techniques like boundary conditions.&lt;/p&gt;

&lt;p&gt;software testing imperative as it identifies any issues and defects with the written code so they can fix before the software product is delivered. Improved the quality&lt;/p&gt;

&lt;p&gt;software test is important if there are any bugs or errors in the software, they can be identified early and fixed before the software product is delivered.&lt;br&gt;
The testing of software is the wide array of benefits. The cost effectiveness of the project happens to be the one of the reasons why the companies go software testing servies&lt;/p&gt;

</description>
    </item>
    <item>
      <title>LCSAJ TESTING</title>
      <dc:creator>karthicks</dc:creator>
      <pubDate>Thu, 25 Jan 2024 00:02:24 +0000</pubDate>
      <link>https://dev.to/karthi27/lcsaj-testing-52pc</link>
      <guid>https://dev.to/karthi27/lcsaj-testing-52pc</guid>
      <description>&lt;p&gt;LCSAJ Stands for Linear Code Sequence and Jump. LCSAJ testing is a white-box testing methodology used to determine the code coverage. It helps in designing new tests cases which can increase the coverage of the code under test. Once the code coverage reaches a certain level we can stop the testing. Hence LCSAJ methodology helps in determine when to stop the testing on the software. White-box testing is a software testing technique in which we test the internal structure and the software code under the test.&lt;br&gt;
Its primary use is with dynamic software analysis to help answer the question. Dynamic software analysis is used to measure the quality and efficacy of software teat data, where the quantification is performed in terms of structural units of the code under test&lt;/p&gt;

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