<?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 - Status</title>
    <link>https://xrmlabs.com/About-Us/XRMs-Blog/term/2565/locale/en-US/Blog-Status</link>
    <description />
    <managingEditor>sales@xrmlabs.com</managingEditor>
    <pubDate>Mon, 20 Apr 2026 22:36:05 GMT</pubDate>
    <lastBuildDate>Mon, 20 Apr 2026 22:36:05 GMT</lastBuildDate>
    <category>Status</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=2565" rel="self" type="application/rss+xml" />
    <item>
      <title>Overview of HTTP Status Codes for Software Testers</title>
      <link>https://xrmlabs.com/About-Us/XRMs-Blog/Post/8495/Overview-of-HTTP-Status-Codes-for-Software-Testers</link>
      <description>&lt;p&gt;&lt;strong&gt;Overview of HTTP Status Codes for Software Testers&lt;/strong&gt;&lt;br /&gt;
&lt;br /&gt;
HTTP status codes are three-digit numbers that define the present status of a client&amp;#39;s request to a server. These codes are returned by the server as a response to a client&amp;#39;s HTTP request. HTTP status codes indicate whether the request was successful, failed, or redirected to another resource.&lt;br /&gt;
&lt;br /&gt;
A request is made to the server (where the website is being hosted) each time a Uniform Resource Locator (URL) is entered into the client browser. In other words, the client sends a Hypertext Transfer Protocol (HTTP) request to the server, and the server replies by returning an HTTP status code to the client, indicating whether the request was successful or not. The server answers when you submit the request via the HTTP protocol.&lt;br /&gt;
&amp;nbsp;&lt;/p&gt;
&lt;quillbot-extension-portal&gt;&lt;/quillbot-extension-portal&gt;</description>
      <category>HTTP Status</category>
      <category>Response code</category>
      <category>Software Testing</category>
      <category>Status</category>
      <guid isPermaLink="true">https://xrmlabs.com/About-Us/XRMs-Blog/Post/8495/Overview-of-HTTP-Status-Codes-for-Software-Testers</guid>
      <pubDate>Tue, 02 May 2023 10:08:00 GMT</pubDate>
      <blog:publishedon>2023-05-02 10:08:00Z</blog:publishedon>
    </item>
    <item>
      <title>what is test case in software testing?</title>
      <link>https://xrmlabs.com/About-Us/XRMs-Blog/Post/8461/what-is-test-case-in-software-testing</link>
      <description>&lt;p&gt;A test case is described as a set of scenarios under which a tester decides whether or not an application is operating in accordance with the needs of the customer. Preconditions, case name, input requirements, and anticipated outcome are all included in test case design. An activity at the first level, test cases are derived from test scenarios.&lt;br /&gt;
It is a comprehensive document that includes all relevant inputs (both positive and negative) as well as the navigational steps required for the test execution procedure. Writing test cases is an one-time activity that can be utilised for regression testing in the future.&lt;/p&gt;
&lt;quillbot-extension-portal&gt;&lt;/quillbot-extension-portal&gt;</description>
      <category>Expected Results</category>
      <category>how to write test case</category>
      <category>Status</category>
      <category>Test Objective</category>
      <category>Testcase ID</category>
      <category>Testing</category>
      <guid isPermaLink="true">https://xrmlabs.com/About-Us/XRMs-Blog/Post/8461/what-is-test-case-in-software-testing</guid>
      <pubDate>Mon, 19 Dec 2022 18:40:00 GMT</pubDate>
      <blog:publishedon>2022-12-19 18:40:00Z</blog:publishedon>
    </item>
  </channel>
</rss>