<?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: abhishek swamy</title>
    <description>The latest articles on DEV Community by abhishek swamy (@abhisheksam).</description>
    <link>https://dev.to/abhisheksam</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%2F1163840%2F3b1a8f2e-5f08-41ef-869c-18e96e2513c2.png</url>
      <title>DEV Community: abhishek swamy</title>
      <link>https://dev.to/abhisheksam</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/abhisheksam"/>
    <language>en</language>
    <item>
      <title>TASK 1</title>
      <dc:creator>abhishek swamy</dc:creator>
      <pubDate>Fri, 06 Sep 2024 06:30:13 +0000</pubDate>
      <link>https://dev.to/abhisheksam/task-1-oi</link>
      <guid>https://dev.to/abhisheksam/task-1-oi</guid>
      <description>&lt;p&gt;Q: What is software testing?, What to we need to know about software testing?, What is the relevance of software testing?&lt;/p&gt;

&lt;p&gt;A: Software testing is nothing but to test a particular software to make sure that the software is bug free/defect free in order to deliver a quality product to the customer/end users according to their requirements.&lt;/p&gt;

&lt;p&gt;Software testing is a very important phase for any given software in to deliver a quality product to the end users.&lt;/p&gt;

&lt;p&gt;The software testing is part of SDLC(software development life cycle) and this consists of 6 stage and they are&lt;/p&gt;

&lt;p&gt;requirement analysis&lt;br&gt;
designing&lt;br&gt;
development&lt;br&gt;
testing&lt;br&gt;
deployment&lt;br&gt;
maintenance&lt;br&gt;
Without testing a particular software it cannot be launched or deployed to the end users. It is very important to test the software to prevent bugs and to improve performance of the software.&lt;/p&gt;

&lt;p&gt;Software testing helps in identifying defects and issues in the development process so that they are fixed before deployment or prior to launch. This process helps to ensure that only quality products are distributed to the customers which results to customer satisfaction and trust.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>TASK 4</title>
      <dc:creator>abhishek swamy</dc:creator>
      <pubDate>Sat, 01 Jun 2024 09:05:54 +0000</pubDate>
      <link>https://dev.to/abhisheksam/task-4-65b</link>
      <guid>https://dev.to/abhisheksam/task-4-65b</guid>
      <description>&lt;p&gt;Q- What is manual testing? What are the benefits and drawbacks?&lt;/p&gt;

&lt;p&gt;A- Manual testing is a type of testing where all the functionalities of the software are tested manually by testers based on customer requirement. It is to check whether all the functionalities are behaving/working as expected in order to deliver a quality and bug free product to the customers/clients.&lt;/p&gt;

&lt;p&gt;: Benefits of manual testing&lt;/p&gt;

&lt;p&gt;Human intelligence is used to identify bugs in manual testing.&lt;br&gt;
programing knowledge is not required.&lt;br&gt;
more useful to find potential defects with the help of human observation.&lt;br&gt;
Useful for testing graphical user interface.&lt;br&gt;
: Drawbacks of manual testing&lt;/p&gt;

&lt;p&gt;It is Time consuming.&lt;br&gt;
It requires more man power compared to automation.&lt;br&gt;
Handling large amount of data is impractical in manual testing.&lt;br&gt;
performance testing is impractical in manual&lt;/p&gt;

</description>
    </item>
    <item>
      <title>TASK 3</title>
      <dc:creator>abhishek swamy</dc:creator>
      <pubDate>Sat, 01 Jun 2024 09:03:58 +0000</pubDate>
      <link>https://dev.to/abhisheksam/task-3-50gp</link>
      <guid>https://dev.to/abhisheksam/task-3-50gp</guid>
      <description>&lt;p&gt;Q-Difference between functional testing and non functional testing&lt;/p&gt;

&lt;p&gt;A-Functional testing is a type of software testing where each functions and features of the software are tested to know whether the functionalities are workings as expected or not.&lt;br&gt;
example: new modules have been added to the present build, need to perform regression testing in order to check whether other aspects of the build has been affected by this module or not.&lt;/p&gt;

&lt;p&gt;Non functional testing is a type of testing where the non functional aspects of the software are tested such as load, performance, speed, usability etc.&lt;br&gt;
example: thousands of people trying to login at the same time, in order to test this load testing can be performed.&lt;/p&gt;

&lt;p&gt;Types of functional testing are unit testing, integration testing, system testing, smoke testing, regression testing, etc.&lt;/p&gt;

&lt;p&gt;Types of non functional testing are performance testing, load testing, stress testing, security testing, etc.&lt;/p&gt;

&lt;p&gt;Functional testing is done based on customer requirements and non functional is focused on customer expectations. Functional testing can be done manually where as it is difficult to do non functional testing without the help of tools.&lt;/p&gt;

&lt;p&gt;Both functional and non functional are equally important in order to deliver a finished and quality product to the clients/customers/end users.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>TASK 2</title>
      <dc:creator>abhishek swamy</dc:creator>
      <pubDate>Sat, 01 Jun 2024 09:02:52 +0000</pubDate>
      <link>https://dev.to/abhisheksam/task-2-3ah8</link>
      <guid>https://dev.to/abhisheksam/task-2-3ah8</guid>
      <description>&lt;p&gt;Boundary value analysis -: boundary values are the values which contain the lower limit and upper limit of the variable. the values within the limit will be valid and the values outside the limit will be invalid.&lt;br&gt;
for example: The password should contain numbers from 1-100&lt;/p&gt;

&lt;p&gt;A=1 , B=100&lt;/p&gt;

&lt;p&gt;A-1,A,A+1,B-1,B,B+1&lt;/p&gt;

&lt;p&gt;0,1,2,99,100,101&lt;/p&gt;

&lt;p&gt;0 and 101 --- invalid input&lt;/p&gt;

&lt;p&gt;1,2,99,100 --- valid input&lt;/p&gt;

&lt;p&gt;Decision table :- A decision table is a form of documenting the decisions or actions based on certain set of conditions.&lt;br&gt;
formula 2^n --- n = no. of test conditions&lt;/p&gt;

&lt;p&gt;for example: We have to sign up in amazon we have 3 conditions&lt;br&gt;
1: User name, 2:user email id, 3:phone number(optional)&lt;/p&gt;

&lt;p&gt;no of condition - 3&lt;/p&gt;

&lt;p&gt;formula 2^3=8&lt;/p&gt;

&lt;p&gt;Input                                     Output&lt;br&gt;
Name Email id Phone number&lt;/p&gt;

&lt;p&gt;T T T T&lt;br&gt;
T T F T&lt;br&gt;
F T T F&lt;br&gt;
F F T F&lt;br&gt;
F F F F&lt;br&gt;
T F T F&lt;br&gt;
T F F F&lt;br&gt;
F T F F&lt;/p&gt;

&lt;p&gt;Use case testing :- Use case testing is a type of black box testing and is done using the use case diagram which is created by the developer, it is to identify the test cases that form a part of the entire system from start to finish.&lt;/p&gt;

&lt;p&gt;LCSAJ technique: It stands for linear code sequence and jump technique which is a white box testing technique to identify the code coverage. it is to identify how many codes have been executed with the existing test cases. it helps to design new testcases&lt;/p&gt;

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