<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:blog="http://dnn-connect.org/blog/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/">
  <channel>
    <title>Blog - good and effective test</title>
    <link>https://xrmlabs.com/About-Us/XRMs-Blog/term/203/locale/en-US/Blog-good-and-effective-test</link>
    <description />
    <managingEditor>sales@xrmlabs.com</managingEditor>
    <pubDate>Mon, 20 Apr 2026 21:07:42 GMT</pubDate>
    <lastBuildDate>Mon, 20 Apr 2026 21:07:42 GMT</lastBuildDate>
    <category>good and effective test</category>
    <generator>DotNetNuke Blog RSS Generator Version 6.5.2.0</generator>
    <ttl>30</ttl>
    <atom:link href="https://xrmlabs.com/DesktopModules/Blog/API/RSS/Get?moduleid=440&amp;tabid=94&amp;term=203" rel="self" type="application/rss+xml" />
    <item>
      <title>Guidelines to write an effective test case</title>
      <link>https://xrmlabs.com/About-Us/XRMs-Blog/Post/370/Guidelines-to-write-an-effective-test-case</link>
      <description>&lt;p&gt;Ability to write effective test case it can acquire by testing experience and carefully studying the requirement and the software that is going through test. In this blog I will discuss how to write an effective test case. While creating a test case it should be well categorised like functional, business, navigational, validation error, etc.&amp;nbsp; To get a better understanding to the case as looking to its category user will know it is related to which part of the application/software.&amp;nbsp;&lt;/p&gt;
</description>
      <category>good and effective test</category>
      <category>Guidelines to write an effective test case</category>
      <category>how to write test case</category>
      <category>Testing Tools</category>
      <guid isPermaLink="true">https://xrmlabs.com/About-Us/XRMs-Blog/Post/370/Guidelines-to-write-an-effective-test-case</guid>
      <pubDate>Sat, 10 Sep 2022 16:19:00 GMT</pubDate>
      <blog:publishedon>2022-09-10 16:19:00Z</blog:publishedon>
    </item>
  </channel>
</rss>