<?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: FinTestSoftware</title>
    <description>The latest articles on DEV Community by FinTestSoftware (@fintestsoftware).</description>
    <link>https://dev.to/fintestsoftware</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%2F464091%2Fcbfc1ec8-089e-4c61-ab90-3d7961b27279.png</url>
      <title>DEV Community: FinTestSoftware</title>
      <link>https://dev.to/fintestsoftware</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/fintestsoftware"/>
    <language>en</language>
    <item>
      <title>Testing Scenarios
</title>
      <dc:creator>FinTestSoftware</dc:creator>
      <pubDate>Mon, 12 Oct 2020 13:01:54 +0000</pubDate>
      <link>https://dev.to/fintestsoftware/testing-scenarios-2k0e</link>
      <guid>https://dev.to/fintestsoftware/testing-scenarios-2k0e</guid>
      <description>&lt;p&gt;During the test strategy and management, and also the quality control stage of the implemented functionality, test documentation is used, which contains standard and alternative application work-scripts used in testing the next version of the application.&lt;br&gt;
The test documentation consists of test scenarios, that is, a specially designed description of the sequence of actions in the system and expected behavior. Test scenarios are used for various types of manual testing:&lt;br&gt;
Functional testing;&lt;br&gt;
Acceptance testing;&lt;br&gt;
Load tests or stress tests;&lt;br&gt;
research testing;&lt;br&gt;
smoke testing, etc.&lt;br&gt;
In order to develop test scenarios and perform tests, testing management systems are used to significantly improve the performance of test designers and testers, as well as to ensure that the quality level of applications is visible to all participants in the project. Read more: &lt;a href="https://fin-test.net/services/test-strategy-and-management/?utm_source=linkbilder"&gt;https://fin-test.net/services/test-strategy-and-management/?utm_source=linkbilder&lt;/a&gt;&lt;/p&gt;

</description>
      <category>casetest</category>
      <category>testing</category>
      <category>testinasearch</category>
    </item>
    <item>
      <title>Testing Acceptance</title>
      <dc:creator>FinTestSoftware</dc:creator>
      <pubDate>Sat, 05 Sep 2020 16:44:08 +0000</pubDate>
      <link>https://dev.to/fintestsoftware/testing-acceptance-2919</link>
      <guid>https://dev.to/fintestsoftware/testing-acceptance-2919</guid>
      <description>&lt;p&gt;User acceptance testing, or, as it is also known, end-user testing is one of the key phases of the development and testing life cycle. This functionality testing technique is applied during the final stages of the development before the system is released. The main purpose of the UAT is to get the client’s approval of the created application. As any system is created for customers, their estimation is highly important. In the process of executing acceptance tests, real-world scenarios are simulated in order to confirm that the system meets the testing criteria and therefore can be released to the market. Checking such features as functionality, usability, performance, and UI may be involved as well. Take into consideration, that even though the user acceptance test is carried out right before the production, it is important to have enough time for fixing the detected bugs. This ensures delivering a high-quality and satisfactory application. See the details.&lt;br&gt;
UAT is categorized into several types, including alpha and beta testing, contract, regulation, and operational acceptance testing. The choice of the method depends on your circumstances and goals.&lt;/p&gt;

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