<?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>Forem: Kshitij kumar</title>
    <description>The latest articles on Forem by Kshitij kumar (@kshitijkumar05).</description>
    <link>https://forem.com/kshitijkumar05</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%2F533665%2Fd63e0531-1fec-4a17-81be-389c932fac01.jpeg</url>
      <title>Forem: Kshitij kumar</title>
      <link>https://forem.com/kshitijkumar05</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/kshitijkumar05"/>
    <language>en</language>
    <item>
      <title>LoadRunner : A Performance testing tool</title>
      <dc:creator>Kshitij kumar</dc:creator>
      <pubDate>Tue, 07 Sep 2021 15:29:06 +0000</pubDate>
      <link>https://forem.com/kshitijkumar05/loadrunner-a-performance-testing-tool-53l5</link>
      <guid>https://forem.com/kshitijkumar05/loadrunner-a-performance-testing-tool-53l5</guid>
      <description>&lt;p&gt;&lt;strong&gt;LoadRunner&lt;/strong&gt; is one of the biggest name in the performance testing world. LoadRunner has a variety of protocol support which covers nearly all types of the software platform.&lt;br&gt;
&lt;em&gt;LoadRunner&lt;/em&gt; is developed by Mercury in 1999 and acquired by HPE in 2006 and named as &lt;em&gt;HP LoadRunner&lt;/em&gt;. Later on, after the merger of Micro Focus with HPE gave it a new name called &lt;strong&gt;Micro Focus LoadRunner&lt;/strong&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Functioning of LoadRunner
&lt;/h2&gt;

&lt;p&gt;&lt;em&gt;LoadRunner&lt;/em&gt; works on the concept of recording and replaying the user activities and generating the desired load on the server. It simply simulates the real world user’s actions and helps to identify the performance of the software application or system by generating virtual load.&lt;/p&gt;

&lt;p&gt;The main steps include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;em&gt;Recording/Scripting&lt;/em&gt; : To capture the user action into a script. These scripts are run by generating virtual users.&lt;/li&gt;
&lt;li&gt;
&lt;em&gt;Test Execution&lt;/em&gt; : Replaying the script along with virtual load to simulate the real-world situation in the test environment.&lt;/li&gt;
&lt;li&gt;
&lt;em&gt;Result Analysis&lt;/em&gt; : To provide accurate result in terms of load handling capacity and responsiveness of the application. the Analysis tool generates the report (in pdf, HTML, excel etc. format) which concludes the test result.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  LoadRunner Components
&lt;/h2&gt;

&lt;p&gt;Micro Focus LoadRunner has the following components:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Virtual User Generator or VuGen&lt;/strong&gt; : It records end-user business processes and creates an automated test script in the form of programming language. The generated script is called as &lt;em&gt;VuGen Script&lt;/em&gt; or &lt;em&gt;Test Script&lt;/em&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Load Generators&lt;/strong&gt; :  These are machines which generate the virtual load as per the requirement. During test execution, the Controller distributes each Vuser in the scenario to a load generator. Load generator is also used to simulates the geographical location of the users.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Controller&lt;/strong&gt; : It organizes, drives, manages, and monitors the load test. A controller is also used for workload modelling. Workload Modelling involves the creation of a test scenario as per NFR (Non-Functional Requirement).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Agent&lt;/strong&gt; : The LoadRunner agent sets-up a communication between the Controller and the Load Generator.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Analysis&lt;/strong&gt; : It helps to view, dissect and compare the results of the load tests. Analysis tool displays the result graphs and statistics to validate the test result against the defined NFRs (Non-functional requirement) and to find out the bottleneck (performance bugs). The analysis tool also generates a report based on the test result.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Performance Testing Roadmap
&lt;/h2&gt;

&lt;p&gt;Performance Testing Roadmap can be broadly divided into 5 steps:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Planning for Load Test&lt;/li&gt;
&lt;li&gt;Create VUGen Scripts&lt;/li&gt;
&lt;li&gt;Scenario Creation&lt;/li&gt;
&lt;li&gt;Scenario Execution&lt;/li&gt;
&lt;li&gt;Results Analysis (followed by system tweaking)&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why to choose LoadRunner?
&lt;/h2&gt;

&lt;p&gt;There are many reasons to choose Microfocus LoadRunner as a Performance Testing tool:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;LoadRunner has a simple and interactive user interface.&lt;/li&gt;
&lt;li&gt;It removes the drawbacks of manual performance testing with its user-friendly components.&lt;/li&gt;
&lt;li&gt;LoadRunner limits the requirement of excess hardware. Since there are no physical users so a single Load Generator machine can generate multiple user load and reduces the requirement of hardware or physical machines.&lt;/li&gt;
&lt;li&gt;Easy correlation method (to handle the dynamic values coming from the server). Also, intelligent auto-correlation feature.&lt;/li&gt;
&lt;li&gt;Supports mobile and cloud performance testing.&lt;/li&gt;
&lt;li&gt;The flexibility of the controller helps to create the user load test of any pattern.&lt;/li&gt;
&lt;li&gt;Live graphs and statistics of client-side performance metric during the test.&lt;/li&gt;
&lt;li&gt;LoadRunner also supports to monitor the network and server resources to identify the bottleneck.&lt;/li&gt;
&lt;li&gt;A wide variety of graphs helps in result analysis.&lt;/li&gt;
&lt;li&gt;Option to generate the reports in multiple formats.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;To learn more about LoadRunner you can also visit:&lt;br&gt;
&lt;a href="https://www.perfmatrix.com/micro-focus-loadrunner-tutorial/"&gt;https://www.perfmatrix.com/micro-focus-loadrunner-tutorial/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>testing</category>
      <category>performance</category>
      <category>beginners</category>
    </item>
    <item>
      <title>Performance Testing : An Introduction</title>
      <dc:creator>Kshitij kumar</dc:creator>
      <pubDate>Tue, 07 Sep 2021 13:24:47 +0000</pubDate>
      <link>https://forem.com/kshitijkumar05/performance-testing-an-introduction-12kl</link>
      <guid>https://forem.com/kshitijkumar05/performance-testing-an-introduction-12kl</guid>
      <description>&lt;p&gt;&lt;em&gt;Software testing&lt;/em&gt; is performed to check whether actual software matches expected requirement and to ensure that product is error free. There are various type of software testing and &lt;strong&gt;Performance testing&lt;/strong&gt; is one of them.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is Performance Testing?
&lt;/h2&gt;

&lt;p&gt;&lt;em&gt;Performance Testing&lt;/em&gt; is a non-functional testing method performed to determine the system performance in terms of sensitivity, reactivity and stability under a particular workload. It is also known as &lt;strong&gt;Perf Testing&lt;/strong&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Performance Testing Attributes
&lt;/h2&gt;

&lt;p&gt;Following are the four attributes of &lt;em&gt;performance testing&lt;/em&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;em&gt;Speed&lt;/em&gt; : It determines whether the software product responds rapidly.&lt;/li&gt;
&lt;li&gt;
&lt;em&gt;Scalability&lt;/em&gt; : It determines amount of load the software product can handle at a time.&lt;/li&gt;
&lt;li&gt;
&lt;em&gt;Stability&lt;/em&gt; : It determines whether the software product is stable in case of varying workloads.&lt;/li&gt;
&lt;li&gt;
&lt;em&gt;Reliability&lt;/em&gt; : It determines whether the software product is secure or not.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why do Performance Testing?
&lt;/h2&gt;

&lt;p&gt;Features and Functionality supported by a software system is not the only concern. A software application’s performance like its speed, response time, reliability, stability, resource usage and scalability do matter. The goal of&lt;br&gt;
&lt;em&gt;Performance testing&lt;/em&gt; is not to find bugs but to eliminate performance bottlenecks.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Only a 5-minute downtime of Google.com (19-Aug-13) is estimated to cost the search giant as much as $545,000.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;It’s estimated that companies lost sales worth $1100 per second due to a recent Amazon Web Service Outage.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So, to avoid or minimize such loss, performance testing is important.&lt;/p&gt;

&lt;h2&gt;
  
  
  Types of Performance Testing
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Load testing&lt;/strong&gt; – It checks the application’s ability to perform under anticipated user loads. The objective is to identify performance bottlenecks before the software application goes live.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Stress testing&lt;/strong&gt; – It involves testing an application under extreme workloads to see how it handles high traffic or data processing. The objective is to identify the breaking point of an application.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Endurance testing&lt;/strong&gt; – It is done to make sure the software can handle the expected load over a long period of time.&lt;br&gt;
Spike testing – tests the software’s reaction to sudden large spikes in the load generated by users.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Volume testing&lt;/strong&gt; – Under &lt;em&gt;Volume testing&lt;/em&gt; large no. of. data is populated in a database and the overall software system’s behavior is monitored. The objective is to check software application’s performance under varying database volumes.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Scalability testing&lt;/strong&gt; – The objective of scalability testing is to determine the software application’s effectiveness in “scaling up” to support an increase in user load. It helps plan capacity addition to your software system.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Performance Testing tools
&lt;/h2&gt;

&lt;p&gt;Some common tools used for performance testing are mentioned below:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="http://jmeter.apache.org/"&gt;Jmeter&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="http://opensta.org/"&gt;Open STA&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="http://www.hp.com/"&gt;Load Runner&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="http://www.radview.com/"&gt;Web Load&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To learn more about performance testing you can visit : &lt;a href="https://www.perfmatrix.com/performance-testing-tutorial/"&gt;https://www.perfmatrix.com/performance-testing-tutorial/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>testing</category>
      <category>performance</category>
      <category>beginners</category>
      <category>blogs</category>
    </item>
    <item>
      <title>Markdown Syntax Element to make READMEs attractive</title>
      <dc:creator>Kshitij kumar</dc:creator>
      <pubDate>Sat, 05 Dec 2020 19:37:28 +0000</pubDate>
      <link>https://forem.com/kshitijkumar05/markdown-syntax-element-to-make-readmes-attractive-1emp</link>
      <guid>https://forem.com/kshitijkumar05/markdown-syntax-element-to-make-readmes-attractive-1emp</guid>
      <description>&lt;p&gt;A README is a text file that introduces and explains a project. It contains information that is commonly required to understand what the project is about. While READMEs can be written in any text file format, the most common one that is used nowadays is Markdown. It allows you to add some lightweight formatting.&lt;/p&gt;

&lt;p&gt;Some of the common syntax to make Markdown files attractive are:&lt;/p&gt;

&lt;p&gt;&lt;code&gt; Heading &lt;/code&gt;&lt;br&gt;
For heading we use #. # represent heading1 (h1). The numbers of # used correspond to heading level. For example for heading6 (h6) ###### is used.&lt;/p&gt;

&lt;p&gt;&lt;code&gt; Paragraph &lt;/code&gt;&lt;br&gt;
To create paragraphs, use a blank line to separate one or more lines of text.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;  Bold &lt;/code&gt;&lt;br&gt;
To bold text, add two asterisks (**) or underscores(__) before and after a word or phrase.&lt;/p&gt;

&lt;p&gt;&lt;code&gt; Italic &lt;/code&gt;&lt;br&gt;
To make text Italic, add one asterisk(*) or underscore(_) before and after a word or phrase.&lt;/p&gt;

&lt;p&gt;&lt;code&gt; Bold and Italic &lt;/code&gt;&lt;br&gt;
To make text both Bold and Italic add three asterisk(***) or underscore(___) before and after a word or phrase.&lt;/p&gt;

&lt;p&gt;&lt;code&gt; Blockquotes &lt;/code&gt;&lt;br&gt;
To create a blockquote, add a &amp;gt; in front of a paragraph.&lt;/p&gt;

&lt;p&gt;&lt;code&gt; Ordered Lists &lt;/code&gt;&lt;br&gt;
To create an ordered list, add line items with numbers followed by periods. The numbers don’t have to be in numerical order, but the list should start with the number one.  &lt;/p&gt;

&lt;p&gt;&lt;code&gt; Unordered Lists &lt;/code&gt;&lt;br&gt;
To create an unordered list, add dashes (-), asterisks (&lt;em&gt;), or plus signs (+) in front of line items. -,&lt;/em&gt;,+ will be changed into bullets.&lt;/p&gt;

&lt;p&gt;&lt;code&gt; Code &lt;/code&gt;&lt;br&gt;
To denote a word or phrase as code, enclose it in backticks (`).&lt;/p&gt;

&lt;p&gt;&lt;code&gt;URLs and Email Addresses&lt;/code&gt;&lt;br&gt;
To quickly turn a URL or email address into a link, enclose it in angle(&amp;lt;&amp;gt;) brackets.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;You can find all the syntax and information related to markdown at&lt;/em&gt;&lt;/strong&gt; &lt;br&gt;
&lt;a href="https://daringfireball.net/projects/markdown"&gt;https://daringfireball.net/projects/markdown&lt;/a&gt;&lt;/p&gt;

</description>
      <category>github</category>
      <category>markdown</category>
      <category>webdev</category>
      <category>beginners</category>
    </item>
  </channel>
</rss>
