<?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: samu santhiraj</title>
    <description>The latest articles on DEV Community by samu santhiraj (@samu_deva).</description>
    <link>https://dev.to/samu_deva</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%2F1530405%2Fe8fe5174-1cbb-4ff9-bf72-85d41f55dc9c.jpg</url>
      <title>DEV Community: samu santhiraj</title>
      <link>https://dev.to/samu_deva</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/samu_deva"/>
    <language>en</language>
    <item>
      <title>Selenium</title>
      <dc:creator>samu santhiraj</dc:creator>
      <pubDate>Wed, 28 Aug 2024 16:48:18 +0000</pubDate>
      <link>https://dev.to/samu_deva/selenium-3g0i</link>
      <guid>https://dev.to/samu_deva/selenium-3g0i</guid>
      <description>&lt;p&gt;Selenium :&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Selenium is one of the most widely used open source web User Interface automation testing suite .It can be easily deployed on platforms such as windows ,Linux ,Solaris and Macintosh.&lt;/li&gt;
&lt;li&gt;Selenium supports automation across different browsers , platforms and programming languages.
Importance of testing in Selenium Automation:
Manual testing can be time consuming and prone to human errors. Selenium Automation allows test to be executed quickly and accurately, reducing human mistakes and ensuring consistent test results.
Selenium allows developers and testers to automate the testing of web applications across different browsers and platforms.
1.Language support(python ,JavaScript)
2.Browser support(google chrome, IE)
3.Scalability(test cases ,maximum test coverage)
4.Reusable test script(save time &amp;amp; effort in test script creation &amp;amp; maintenance)
5.Parallel testing(parallel testing execution &amp;amp;allowing multiple tests to run concurrently)
6.Documentation and Reporting
7.User Experience testing (user interactions &amp;amp;behavior)
8.Continuous integration and Continuous Deployment
Selenium automation testing tools:
1.Selenium WebDriver(interaction with web browsers ,real user , supports various programming languages&amp;amp; dynamic web elements)
2.Selenium Integrated Development Environment(IDE)(recording and playing back test scripts &amp;amp; small scale automation)
3.Selenium Grid(parallel execution &amp;amp; multiple browsers)
4.Selenese (set of commands used in selenium IDE)
5.Browser Specific Driver(chrome driver)&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Use of Selenium automation:&lt;br&gt;
1.Efficient &amp;amp; accurate web application&lt;br&gt;
2.The ability to test your web application on multiple browsers and OS&lt;br&gt;
3.To run more than one test at the same time&lt;/p&gt;

</description>
    </item>
    <item>
      <title>MANUAL TESTING</title>
      <dc:creator>samu santhiraj</dc:creator>
      <pubDate>Wed, 05 Jun 2024 17:23:51 +0000</pubDate>
      <link>https://dev.to/samu_deva/manual-testing-4666</link>
      <guid>https://dev.to/samu_deva/manual-testing-4666</guid>
      <description>&lt;p&gt;MANUALTESTING:&lt;br&gt;
Manual testing is a technique to test the software that is carried out using the functions and features of an application . In manual software testing, a tester tests the software by following a set of predefined test cases. In this testing ,testers make test cases for the codes, test the software ,and give the final report about that software. &lt;/p&gt;

&lt;p&gt;Characteristics of MANUAL TESTING:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Human performance&lt;/li&gt;
&lt;li&gt;Investigative Testing&lt;/li&gt;
&lt;li&gt;Flexibility&lt;/li&gt;
&lt;li&gt;Initial testing&lt;/li&gt;
&lt;li&gt;Examining complex situations&lt;/li&gt;
&lt;li&gt;Testing User interfaces&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Need for Manual Testing:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Bug-free and stability(stable ,requirement&amp;amp; delivers a stable product to the customers)&lt;/li&gt;
&lt;li&gt;Familiarity(write correct test cases for the software)&lt;/li&gt;
&lt;li&gt;Fixing the defects&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Manual testing process:&lt;br&gt;
Unit testing:&lt;br&gt;
Unit Testing is also called Module Testing or Component Testing. It is done to check whether the individual unit or module of the source code is working properly. &lt;/p&gt;

&lt;p&gt;Integration testing:&lt;br&gt;
Integration Testing is the process of testing the interface between the two software units. &lt;/p&gt;

&lt;p&gt;Regression testing:&lt;br&gt;
Repeated testing of an already tested program, after modification, to discover any defects introduced or uncovered as a result of the changes in the software being tested or in another related or unrelated software components.&lt;br&gt;
user interface testing:&lt;br&gt;
security testing:&lt;br&gt;
performance &amp;amp;acceptance testing:&lt;/p&gt;

&lt;p&gt;Example: car is a software&lt;br&gt;
Unit testing--&amp;gt;Engine&lt;/p&gt;

&lt;p&gt;Types of Manual testing:&lt;br&gt;
1.Black Box Testing:&lt;br&gt;
Black Box Testing is a software testing method in which testers evaluate the functionality of the software under test without looking at the internal code structure. This can be applied to every level of software testing such as Unit, Integration, System and Acceptance Testing. &lt;/p&gt;

&lt;p&gt;2.White Box Testing:&lt;br&gt;
White Box Testing is also called as Glass Box, Clear Box, and Structural Testing. It is based on applications internal code structure. In white-box testing, an internal perspective of the system, as well as programming skills, are used to design test cases.&lt;/p&gt;

&lt;p&gt;3.Grey Box Testing:&lt;br&gt;
Grey box is the combination of both White Box and Black Box Testing. The tester who works on this type of testing needs to have access to design documents. This helps to create better test cases in this process.&lt;/p&gt;

&lt;p&gt;Benefits of manual testing:&lt;br&gt;
1.Fast and accurate visual feedback(detects almost every bug in the software application)&lt;br&gt;
2.Less expensive(specific type of tool)&lt;br&gt;
3.No coding is required(black box testing method using)&lt;br&gt;
4.Efficient for unplanned changes&lt;/p&gt;

&lt;p&gt;Drawbacks of manual testing:&lt;br&gt;
1.Less reliable(not provide testing on all aspects testing)&lt;br&gt;
2.Can not be reused(separate test cases for new software)&lt;br&gt;
3.Time -consuming&lt;br&gt;
4.Large human resources required&lt;/p&gt;

</description>
    </item>
    <item>
      <title>FUNCTIONAL &amp; NON-FUNCTIONAL TESTING</title>
      <dc:creator>samu santhiraj</dc:creator>
      <pubDate>Tue, 04 Jun 2024 17:21:13 +0000</pubDate>
      <link>https://dev.to/samu_deva/functional-non-functional-testing-1724</link>
      <guid>https://dev.to/samu_deva/functional-non-functional-testing-1724</guid>
      <description>&lt;p&gt;FUNCTIONALITY TESTING:&lt;br&gt;
It is a type of testing to test the feature of the product .Whether it covers all its purpose and list of all functionalities and also to check whether it is created as per the requirements from the SRS or BRS document.&lt;br&gt;
Functional testing is also a type of black box testing that holds the test cases based on the specifications of the component under test.&lt;br&gt;
what the system actually does is functional testing. To verify that each function of the software application behaves as specified in the requirement document. Testing all the functionalities by providing appropriate input to verify whether the actual output is matching the expected output or not. It falls within the scope of black box testing and the testers need not concern about the source code of the application.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;What the system actually does is functional testing&lt;/li&gt;
&lt;li&gt;To ensure that your product meets customer and business requirements and doesn’t have any major bugs&lt;/li&gt;
&lt;li&gt;To verify the accuracy of the software against expected output
4.It is performed before non-functional testing&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Functional Testing types are&lt;br&gt;
• Unit testing&lt;br&gt;
• Smoke testing&lt;br&gt;
• User Acceptance&lt;br&gt;
• Integration Testing&lt;br&gt;
• Regression testing&lt;br&gt;
• Localization&lt;br&gt;
• Globalization&lt;br&gt;
• Interoperability&lt;/p&gt;

&lt;p&gt;EXAMPLE:&lt;br&gt;
Example of functional test case is to verify the login functionality&lt;br&gt;
GPay&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Adding a bank accounts&lt;/li&gt;
&lt;li&gt;Sending and receiving money &lt;/li&gt;
&lt;li&gt;Messaging&lt;/li&gt;
&lt;li&gt;Allowing contacts&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;NON FUNCTIONAL TESTING:&lt;br&gt;
Non functional testing is another type of software testing which is used to check the non functional aspects of a system like the performance the usability readability and so on it helps in testing the readiness of the system&lt;br&gt;
How well the system performs is non-functionality testing. Non-functional testing refers to various aspects of the software such as performance, load, stress, scalability, security, compatibility etc., Main focus is to improve the user experience on how fast the system responds to a request.&lt;/p&gt;

&lt;p&gt;1.How well the system performs is non-functionality testing&lt;br&gt;
2.To ensure that the product stands up to customer expectations&lt;br&gt;
3.To verify the behavior of the software at various load conditions&lt;br&gt;
4.It is performed after functional testing&lt;/p&gt;

&lt;p&gt;Non Functional Testing types &lt;br&gt;
• Performance Testing&lt;br&gt;
• Volume Testing&lt;br&gt;
• Scalability&lt;br&gt;
• Usability Testing&lt;br&gt;
• Load Testing&lt;br&gt;
• Stress Testing&lt;br&gt;
• Compliance Testing&lt;br&gt;
• Portability Testing&lt;br&gt;
• Disaster Recover Testing&lt;br&gt;
EXAMPLE:&lt;br&gt;
google  homepage open&lt;br&gt;
non-functional test case is to check whether the homepage is loading in less than 2 seconds&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Testing Technique</title>
      <dc:creator>samu santhiraj</dc:creator>
      <pubDate>Wed, 29 May 2024 17:42:06 +0000</pubDate>
      <link>https://dev.to/samu_deva/testing-technique-575o</link>
      <guid>https://dev.to/samu_deva/testing-technique-575o</guid>
      <description>&lt;p&gt;BOUNDARY VALUE ANALYSIS&lt;br&gt;
     Boundary value analysis is a software testing technique in which tests are designed to include values at the boundaries between partitions of input values .This helps in identifying errors at the boundaries of input domains .&lt;br&gt;
     It a software testing technique in which tests are designed to include representatives of boundary values in a range.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Lower boundary cases(min)&lt;/li&gt;
&lt;li&gt;Upper boundary cases(max)&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On boundary cases(minmax)&lt;br&gt;
Examples:&lt;br&gt;
  You are going for an adventure park they have a age restriction like this. these are valid data that we will be arriving on if we apply boundary value analysis.&lt;br&gt;
Enter your age(*only 10 to 60 are allowed for this ride)&lt;br&gt;
Invalid                valid                  Invalid&lt;br&gt;
min-1              min max                 max+1&lt;br&gt;
 9                  12                        61&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;More application errors occurs at the boundaries of the input domain.&lt;/li&gt;
&lt;li&gt;Its used to identify errors at boundaries rather than finding those 
that exist in the center of the input domain.&lt;/li&gt;
&lt;/ol&gt;


&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;DECISION TABLE TESTING:&lt;br&gt;
        Decision table testing is a black-box testing technique used to evaluate system behavior based on combination of input conditions or actions. It involves creating a table that captures all possible input combinations and their corresponding expected outputs or actions.&lt;br&gt;
     This technic can also called as cause and effect table ,as it captures the driving factors and the effect in the table format.&lt;br&gt;
 Example:&lt;br&gt;
     You are going for Poorvika mobiles .Membership D1 offer , more then one product D2 offer &amp;amp; credit card offer D3.&lt;br&gt;
                                 D1        D2      D3&lt;br&gt;
Membership offer               offer       -       -&lt;br&gt;
More then 1 product              -       offer     -&lt;br&gt;
credit card                      -         -       offer&lt;br&gt;
credit card + membership       offer       -       offer&lt;br&gt;
new customer                     -         -        -&lt;/p&gt;

&lt;p&gt;USE CASE TESTING:&lt;br&gt;
 Use case is much like a older brother to user stories. Use case is a process of defining the action done by the users on the system and the responses of the system for the corresponding action.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Describes the system behavior end user perspective&lt;/li&gt;
&lt;li&gt;It explains the functionality or requirement, the customer requirement or project requirement can be specify in the use cases.&lt;/li&gt;
&lt;li&gt;use case is a representation of actions which describes the behavior of system to do a particular task.
Example:&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;anna university result&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;                        user         system                 result
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;enter reg. no           valid reg no    check the reg no       positive&lt;br&gt;
enter invalid reg no    invalid reg no  check reg no MSG       negative&lt;br&gt;
                                         "invalid reg no"&lt;/p&gt;

&lt;p&gt;LCSAJ TESTING: &lt;br&gt;
Transparent box&lt;br&gt;
Input--&amp;gt;coding--&amp;gt;output&lt;/p&gt;

&lt;p&gt;LCSAJ stands for “Linear Code Sequence and Jump” testing. It is a white-box testing technique used to assess the coverage of source code within a software program.&lt;br&gt;
 LCSAJ testing focuses on verifying that all linear code sequences and jumps within the code are exercised by test cases. This technique is commonly used in the context of structural testing or code coverage analysis.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The starting line at the beginning of a module or at a line of code that was jumped to by another LCSAJ.&lt;/li&gt;
&lt;li&gt;The end of the LCSAJ at the end of a module or at a line of code where a jump occurs.
3.The target of the jump&lt;/li&gt;
&lt;/ol&gt;

</description>
    </item>
    <item>
      <title>Relevance of Software Testing</title>
      <dc:creator>samu santhiraj</dc:creator>
      <pubDate>Mon, 27 May 2024 17:23:16 +0000</pubDate>
      <link>https://dev.to/samu_deva/relevance-of-software-testing-dh8</link>
      <guid>https://dev.to/samu_deva/relevance-of-software-testing-dh8</guid>
      <description>&lt;ol&gt;
&lt;li&gt;Flexibility and Extensibility
Flexibility is the ability of a software system to adapt to different situations. Extensibility is the quality of being designed to allow the addition of new capability&lt;/li&gt;
&lt;li&gt;Maintainability and Readability&lt;/li&gt;
&lt;li&gt;Performance Efficiency&lt;/li&gt;
&lt;li&gt;Testability  and Manageability&lt;/li&gt;
&lt;li&gt;security&lt;/li&gt;
&lt;/ol&gt;

</description>
    </item>
    <item>
      <title>Need of Software Testing</title>
      <dc:creator>samu santhiraj</dc:creator>
      <pubDate>Mon, 27 May 2024 17:03:40 +0000</pubDate>
      <link>https://dev.to/samu_deva/need-of-software-testing-1i5a</link>
      <guid>https://dev.to/samu_deva/need-of-software-testing-1i5a</guid>
      <description>&lt;ol&gt;
&lt;li&gt;To prevent defects by evaluate work products&lt;/li&gt;
&lt;li&gt;To verify whether all specified requirement have been fulfilled&lt;/li&gt;
&lt;li&gt;To check whether the test object is complete and validate&lt;/li&gt;
&lt;li&gt;To build confidence in the level of quality of the test object&lt;/li&gt;
&lt;li&gt;To find defects and failures
   Verification is the process, to ensure that whether we are building the product right to verify the requirements which we have and to verify whether we are developing the product accordingly or not. Activities involved here are Inspections, Reviews, Walk-throughs

&lt;ol&gt;
&lt;li&gt;To easy our works.&lt;/li&gt;
&lt;li&gt;Determining the performance of the software.&lt;/li&gt;
&lt;li&gt;Discovery and subsequent correction of errors &amp;amp; bugs. 
9.Indicator of system reliability &amp;amp; quality.&lt;/li&gt;
&lt;/ol&gt;


&lt;/li&gt;
&lt;/ol&gt;

</description>
    </item>
    <item>
      <title>Software Testing</title>
      <dc:creator>samu santhiraj</dc:creator>
      <pubDate>Mon, 27 May 2024 16:52:33 +0000</pubDate>
      <link>https://dev.to/samu_deva/software-testing-kcm</link>
      <guid>https://dev.to/samu_deva/software-testing-kcm</guid>
      <description>&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;  Software testing is a way to assess the quality of the software and to reduce the risk of software failure in operation .It is a process used to identify the correctness, completeness and quality of developed computer software.
  Software testing is the process of testing bugs in lines of code of a program that can be performed by manual or automation testing.  Software testing is nothing but collection program. Program return by the developer for solving preface.
   Software testing is thinks only in the terms of pass or fail of a test case and how to break the software.
   Test works only for test life cycle, like design of test cases, and execution. No coding knowledge is required software tester are not expected to reach up to code level and tune the performance
  Some testing does involve the execution of the component being tested such testing called dynamic testing.
  Other testing does not involve the execution of the component being tested such testing called static testing.
Developer thinks how to develop a system and make a functionality work . Developer is limited to Coding part and release to testing team
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;Only coding knowledge is required developers are only expected to code the functionality which is expected by the customer.&lt;/p&gt;

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