<?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: D-Pavithra</title>
    <description>The latest articles on DEV Community by D-Pavithra (@dpavithra).</description>
    <link>https://dev.to/dpavithra</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%2F1141730%2Fbd2837c7-65f7-4c15-b8f9-40714c0d614a.png</url>
      <title>DEV Community: D-Pavithra</title>
      <link>https://dev.to/dpavithra</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/dpavithra"/>
    <language>en</language>
    <item>
      <title>TASK-1</title>
      <dc:creator>D-Pavithra</dc:creator>
      <pubDate>Sun, 25 Aug 2024 11:19:21 +0000</pubDate>
      <link>https://dev.to/dpavithra/task-1-23h3</link>
      <guid>https://dev.to/dpavithra/task-1-23h3</guid>
      <description>&lt;p&gt;TASK 1&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;What is Software Testing? What do we need to know about Software Testing? What is the relevance of Software testing?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Software Testing:&lt;br&gt;
• A testing process done to verify whether the developed product is meeting the entire customer/client requirement is called Software Testing. In other words, after the development of the software the process done to check whether the developed product is right and it meets the customer needs are called Software Testing. &lt;br&gt;
• Software Testing is carried by two main methods i.e., Verification and Validation. &lt;br&gt;
• Verification: To check whether the developed product meets the customer requirements or not is called Verification. &lt;br&gt;
o   In other words, “Are we building the software right?”&lt;br&gt;
o   It is process oriented.&lt;br&gt;
• Validation: To check whether the developed product meets the user needs is called Validation. &lt;br&gt;
o   In other words, “Are we building the right product?”&lt;br&gt;
o   It is product oriented.&lt;br&gt;
Types of Software Testing:&lt;br&gt;
There are few software testing methodologies as listed below:&lt;br&gt;
 Functional Testing: It involves executing the software and checking its behavior during runtime.&lt;br&gt;
o   Unit Testing: Tests individual components or functions in isolation.&lt;br&gt;
o   Integration Testing: Ensures that different components or systems work together as expected.&lt;br&gt;
o   System Testing: Validates the complete and integrated software system developed.&lt;br&gt;
o   Acceptance Testing: Confirms that the software meets end-user requirements and is ready for deployment.&lt;br&gt;
 Non-Functional Testing: Assesses aspects of the software that are not related to specific functions.&lt;br&gt;
o   Performance Testing: Evaluates the software's responsiveness, speed, and stability under various conditions.&lt;br&gt;
o   Security Testing: Identifies vulnerabilities and ensures the software is protected against threats.&lt;br&gt;
o   Usability Testing: Checks how user-friendly and intuitive the software is.&lt;br&gt;
 Manual Testing: Performed by human testers who execute test cases and evaluate results based on their knowledge and experience.&lt;br&gt;
 Automated Testing: Uses tools and scripts to execute test cases automatically, which is useful for repetitive tasks and large-scale testing.&lt;br&gt;
Relevance of Software Testing:&lt;br&gt;
• Software testing is an important phase in the software development lifecycle for several reasons as below. &lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Ensuring Software Quality
• Testing helps ensure that the software meets performance benchmarks, such as response time and scalability.
• Ensures that the software is user-friendly and provides a good user experience.&lt;/li&gt;
&lt;li&gt;Detecting and Fixing Bugs Early
• Identifying and fixing defects early in the development process is generally less expensive than addressing them after the software has been deployed.
• Early detection of issues reduces the risk of major problems in production, which can lead to costly downtime or failure.&lt;/li&gt;
&lt;li&gt;Validating Requirements
• Testing verifies that the software meets all specified requirements and performs the functions it is supposed to.
• It ensures that the final product aligns with user needs and expectations, increasing user satisfaction.&lt;/li&gt;
&lt;li&gt;Enhancing Security
• Security testing identifies vulnerabilities that could be exploited by attackers, helping to safeguard sensitive data and protect against breaches.
• Ensures that the software adheres to regulatory and industry standards for data protection and security.&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Supporting Development Process&lt;br&gt;
• Testing provides valuable feedback to developers, allowing them to make informed decisions and improvements throughout the development process.&lt;br&gt;
• Test cases and results help document the software’s functionality and behavior, which can be useful for future maintenance and upgrades.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Improving Reliability and User Trust&lt;br&gt;
• Reliable software builds trust with users, leading to higher adoption rates and better overall satisfaction.&lt;br&gt;
• High-quality, well-tested software enhances the reputation of the company or development team, fostering positive reviews and customer loyalty.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Facilitating Continuous Improvement&lt;br&gt;
• In agile and iterative development environments, testing is integral to continuous integration and continuous delivery (CI/CD), ensuring that each iteration or release meets quality standards.&lt;br&gt;
• Regular testing helps integrate user feedback into subsequent versions, leading to continuous improvement and refinement of the software.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

</description>
    </item>
    <item>
      <title>Task 4</title>
      <dc:creator>D-Pavithra</dc:creator>
      <pubDate>Sat, 26 Aug 2023 04:01:43 +0000</pubDate>
      <link>https://dev.to/dpavithra/task-4-2e5d</link>
      <guid>https://dev.to/dpavithra/task-4-2e5d</guid>
      <description>&lt;p&gt;What is manual testing? What are the benefits and drawbacks of manual testing? Give some examples in support of your exam.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Manual testing:&lt;/strong&gt;&lt;br&gt;
The methodology of testing the developed software/application without using any automated tools is called manual testing&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Benefits of manual testing:&lt;/strong&gt; &lt;br&gt;
i) Depends on the human intelligence&lt;br&gt;
ii) Many issues can be identified in this methodology&lt;br&gt;
iii) Can identify the issues outside the code (i.e., UI issues)&lt;br&gt;
iv) There is no usage of any automation tools, the cost of the project will be less&lt;br&gt;
v) Cross browser testing, exploratory testing, acceptance testing can done by manual testing&lt;br&gt;
vi) Manual testing can be done for the applications having frequent changes in GUI&lt;br&gt;
vii) Accurate output can be achieved through this method of testing.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Drawbacks of manual testing:&lt;/strong&gt;&lt;br&gt;
i) Takes longer time for execution, particularly for repeating scenarios&lt;br&gt;
ii) Expensive in case of long run&lt;br&gt;
iii) Test cases cannot be reused for different software&lt;/p&gt;

&lt;p&gt;*&lt;em&gt;Example: *&lt;/em&gt;&lt;br&gt;
i) Completion of regression testing in manual testing method can take a very long time.&lt;br&gt;
ii) Once the fixes are given to any particular module, there is no need of testing the application completely, the test engineer can test that particular module alone.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Task 3</title>
      <dc:creator>D-Pavithra</dc:creator>
      <pubDate>Sun, 20 Aug 2023 05:59:10 +0000</pubDate>
      <link>https://dev.to/dpavithra/task-3-4eeo</link>
      <guid>https://dev.to/dpavithra/task-3-4eeo</guid>
      <description>&lt;p&gt;What is the difference between Functional and Non Functional testing? Give some examples to support your answer.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;&lt;em&gt;Functional testing:&lt;/em&gt;&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;i) Functional testing is a type of software testing, which verifies the functionality requirements of the developed software.&lt;br&gt;
ii) Functionality testing focuses on the user requirements.&lt;br&gt;
iii) It is done during the development phase of the application.&lt;br&gt;
iv) Types of testing followed here are : Unit testing, regression testing, system testing, sanity testing, smoke testing, retesting.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Unit testing:&lt;/em&gt; Validating the smallest part of the component which is developed is called unit testing.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Regression testing:&lt;/em&gt; Testing the complete software after the fix of any bugs in the application is called regression testing.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Smoke testing:&lt;/em&gt; Making sure that the developed build is steady and is suitable for next phase of testing is called smoke testing&lt;/p&gt;

&lt;p&gt;v) Can be done by both manual and automation testing.&lt;br&gt;
vi) *&lt;em&gt;Example: *&lt;/em&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;User unable to add the product which is in stock to the cart in any ecommerce website.&lt;/li&gt;
&lt;li&gt;Ordering through applications like Flipkart, Amazon, Meesho, Zomato&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;&lt;em&gt;Non Functionality testing:&lt;/em&gt;&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;i) Non Functional testing is a type of software testing, which verifies the Non functionality requirements of the developed software.&lt;br&gt;
ii) Non Functionality testing focuses on the user expectations.&lt;br&gt;
iii) It is done after the completion of functionality testing. &lt;br&gt;
iv) Types of testing followed here are: Performance testing, usability testing, stability testing, scalability testing.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Performance testing:&lt;/em&gt; Validation of the application by giving large amount of workload is called performance testing.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Stability testing:&lt;/em&gt; Verifying whether the developed application can run in different environments is called stability testing.&lt;br&gt;
v) Requires automation tools for effective results.&lt;br&gt;
vi) &lt;strong&gt;Example:&lt;/strong&gt; &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The time taken to load any webpage should be less than 3 seconds.&lt;/li&gt;
&lt;li&gt;Increased number of users should not cause any delay or defect in loading the application.&lt;/li&gt;
&lt;/ul&gt;

</description>
    </item>
    <item>
      <title>Task 1</title>
      <dc:creator>D-Pavithra</dc:creator>
      <pubDate>Sat, 19 Aug 2023 06:02:15 +0000</pubDate>
      <link>https://dev.to/dpavithra/task-1-1f1p</link>
      <guid>https://dev.to/dpavithra/task-1-1f1p</guid>
      <description>&lt;p&gt;&lt;strong&gt;What is software testing? what do we need to know about software testing? what is the relevance of software testing?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;_Software testing: _&lt;/strong&gt;&lt;br&gt;
The method of verifying and validating whether the developed application/software is right and working properly, which also meets the requirements of the client is called software testing&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;Things to know about software testing:&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Software testing is done to make the end product error free, user-friendly, improves the product quality and easy maintenance after the deployment&lt;/li&gt;
&lt;li&gt;Proper testcase should be designed.&lt;/li&gt;
&lt;li&gt;The input which we gave should display the expected output (according to the client's requirement).&lt;/li&gt;
&lt;li&gt;Bugs should be captured at the initial stage and should be tracked using any bug tracker tools like JIRA, Bugzilla etc.,&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;em&gt;&lt;strong&gt;Relevance of software testing:&lt;/strong&gt;&lt;/em&gt;&lt;br&gt;
To identify the issues and get it fixed before the deployment of the product to the client. Also to prevent any major the issues during the maintenance phase of the project.&lt;/p&gt;

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