<?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: Prabhusakthi</title>
    <description>The latest articles on DEV Community by Prabhusakthi (@prabhusakthi).</description>
    <link>https://dev.to/prabhusakthi</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%2F1215956%2F1ee24f66-8385-41f7-ae7e-970d4c4c398d.png</url>
      <title>DEV Community: Prabhusakthi</title>
      <link>https://dev.to/prabhusakthi</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/prabhusakthi"/>
    <language>en</language>
    <item>
      <title>What is the difference between waterfall and agile methodologies in SDLC ?</title>
      <dc:creator>Prabhusakthi</dc:creator>
      <pubDate>Thu, 23 Nov 2023 14:46:30 +0000</pubDate>
      <link>https://dev.to/prabhusakthi/what-is-the-difference-between-waterfall-and-agile-methodologies-in-sdlc--28kk</link>
      <guid>https://dev.to/prabhusakthi/what-is-the-difference-between-waterfall-and-agile-methodologies-in-sdlc--28kk</guid>
      <description>&lt;p&gt;AGILE METHODOLOGIES:&lt;/p&gt;

&lt;p&gt;The Agile methodology promotes the continuous interaction of the development and testing during the SDLC process of any project. Unlike the waterfall model, the development and testing activities in the agile model are simultaneous. Agile methodology allows much communication between the customers, developers, testers, and managers.&lt;/p&gt;

&lt;p&gt;In the Agile method, the entire project is divided into small incremental builds. All of these builds are provided in iterations, and each iteration lasts from one to three weeks.&lt;/p&gt;

&lt;p&gt;1.Agile focuses on customer feedback, collaboration, small and rapid releases.&lt;br&gt;
2.Its purpose is to manage complex projects.&lt;br&gt;
3.The Agile produces better application suites with the desired requirements. Moreover, it can quickly adapt according to the changes made on time during the project life.&lt;br&gt;
4.It has a small team size. Therefore, fewer people work on it so that they can move faster.&lt;/p&gt;

&lt;p&gt;Waterfall model:&lt;/p&gt;

&lt;p&gt;It is one of the easiest and traditional model to manage. Because of its traditional development nature, each phase has specific deliverables and a review process. The waterfall model works well in smaller size projects where requirements are easily understandable.&lt;/p&gt;

&lt;p&gt;The waterfall model is a universally accepted SDLC model. In this method, the whole process of software development is divided into various phases. The development in the waterfall model is seen as flowing steadily downwards (like a waterfall) as it is a continuous software development model. This model is named "Waterfall Model", because its diagrammatic representation resembles a cascade of waterfalls. Some important points related to the waterfall model are listed as follows -&lt;/p&gt;

&lt;p&gt;1.Waterfall model is not an ideal model to develop a large scale project size.&lt;br&gt;
2.The requirements in the waterfall model should be clear cut at the beginning time; otherwise, it may lead to a less effective method.&lt;br&gt;
3.In the waterfall model, it is hard to move back in order to make changes in the previous phase.&lt;br&gt;
4.The testing process in the waterfall model starts after the completion of development. So, there is a high chance of bugs to be found later in the project development.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>As a Manual Tester what qualities do you possess? Provide example to illustrate your point</title>
      <dc:creator>Prabhusakthi</dc:creator>
      <pubDate>Thu, 23 Nov 2023 14:34:30 +0000</pubDate>
      <link>https://dev.to/prabhusakthi/as-a-manual-tester-what-qualities-do-you-possess-provide-example-to-illustrate-your-point-2dh2</link>
      <guid>https://dev.to/prabhusakthi/as-a-manual-tester-what-qualities-do-you-possess-provide-example-to-illustrate-your-point-2dh2</guid>
      <description>&lt;p&gt;As a manual tester, there are several qualities that can contribute to your effectiveness and success in the role. Here are some essential qualities:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Attention to Detail: A manual tester needs to have a keen eye for detail to identify even the smallest defects or deviations from expected behavior. Paying attention to every aspect of the software under test helps in thorough testing and ensures high-quality deliverables. For example, during UI testing, a tester with attention to detail would notice misaligned buttons, inconsistent font sizes, or incorrect color schemes that may affect the user experience.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Analytical and Critical Thinking: Manual testers should possess strong analytical and critical thinking skills to understand complex requirements, identify potential test scenarios, and assess the impact of defects on the software. They need to analyze the system’s behavior, think logically, and identify the root cause of issues. For instance, when encountering a functional defect, a tester with analytical skills would investigate the inputs, conditions, and expected outputs to pinpoint the underlying problem.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Communication Skills: Effective communication is crucial for a manual tester to convey information clearly and collaborate effectively with the development team, stakeholders, and other testers. They should be able to document their findings, write clear and concise defect reports, and articulate their testing approach. Additionally, good communication skills help in discussing requirements, clarifying doubts, and participating in meetings or discussions related to testing.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Persistence and Thoroughness: Manual testing often requires persistence and a thorough approach to ensure that all possible test scenarios are covered. Testers should be persistent in finding defects, executing test cases, and retesting resolved issues. They should be thorough in their testing efforts, leaving no stones unturned. For example, when performing regression testing, a persistent tester would thoroughly retest the entire affected functionality, even if the defect fix seems straightforward.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Adaptability and Learning Ability: Manual testers should be adaptable and open to learning. They need to work with different technologies, tools, and domains, and be willing to quickly grasp new concepts. They should stay updated with the latest testing techniques, industry trends, and emerging technologies. For instance, if a manual tester is assigned to test a mobile application after previously working on web applications, their adaptability will help them quickly understand the mobile-specific testing challenges and adapt their approach accordingly.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Time Management and Organization: Effective time management and organizational skills are essential for manual testers to handle multiple tasks, prioritize their work, and meet deadlines. They should be able to plan their testing activities, estimate effort accurately, and efficiently allocate time for different testing tasks. Being organized helps testers keep track of test cases, test data, and test environments. It enables them to work systematically and effectively manage their testing activities.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;These qualities, along with domain knowledge, testing methodologies, and technical proficiency, contribute to a successful career as a manual tester. Developing and honing these qualities will enhance your effectiveness and value as a tester in the software development life cycle.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>what are different SDLC phases</title>
      <dc:creator>Prabhusakthi</dc:creator>
      <pubDate>Thu, 23 Nov 2023 14:30:29 +0000</pubDate>
      <link>https://dev.to/prabhusakthi/what-are-different-sdlc-phases-3g92</link>
      <guid>https://dev.to/prabhusakthi/what-are-different-sdlc-phases-3g92</guid>
      <description>&lt;ol&gt;
&lt;li&gt;Test Planning, &lt;/li&gt;
&lt;li&gt;Test Analysis, &lt;/li&gt;
&lt;li&gt;Test Design, &lt;/li&gt;
&lt;li&gt;Test Environment Setup, &lt;/li&gt;
&lt;li&gt;Test Execution, &lt;/li&gt;
&lt;li&gt;Test Closure, &lt;/li&gt;
&lt;li&gt;Defect Retesting.&lt;/li&gt;
&lt;/ol&gt;

</description>
    </item>
    <item>
      <title>What are different types of Testing ?</title>
      <dc:creator>Prabhusakthi</dc:creator>
      <pubDate>Thu, 23 Nov 2023 14:24:52 +0000</pubDate>
      <link>https://dev.to/prabhusakthi/what-are-different-types-of-testing--3jk4</link>
      <guid>https://dev.to/prabhusakthi/what-are-different-types-of-testing--3jk4</guid>
      <description>&lt;p&gt;Unit Testing&lt;br&gt;
Integration Testing&lt;br&gt;
System Testing&lt;br&gt;
Functional Testing&lt;br&gt;
Acceptance Testing&lt;br&gt;
Smoke Testing&lt;br&gt;
Regression Testing&lt;br&gt;
Performance Testing&lt;br&gt;
Security Testing&lt;br&gt;
User Acceptance Testing&lt;/p&gt;

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