What is Keyword Driven Testing : Frameworks & How to Perform


<p>A modern web application has complex architecture and internal dependencies. And, has to go through different types of testing. Functional testing is one of the most commonly done testing on web applications, before delivering the software.&nbsp;</p>



<p>Functionality and user experience of a web application depends on the performance of the web application. Hence, performance testing is also essential before a release.&nbsp;</p>



<p>Gatling and JMeter are the most used performance testing tools. However to conclude which is the better for performance testing we need to understand the Gatling vs JMeter key differences. In this article, we have explained Gatling vs JMeter in detail.</p>



<div id="toc_container" class="no_bullets"><p class="toc_title">Table Of Contents</p><ul class="toc_list"><li><a href="#Why_Performance_Testing"><span class="toc_number toc_depth_1">1</span> Why Performance Testing?</a></li><li><a href="#What_is_Gatling"><span class="toc_number toc_depth_1">2</span> What is Gatling?</a></li><li><a href="#What_is_Apache_JMeter"><span class="toc_number toc_depth_1">3</span> What is Apache JMeter?</a></li><li><a href="#Gatling_vs_JMeter_Detailed_Comparison"><span class="toc_number toc_depth_1">4</span> Gatling vs JMeter: Detailed Comparison</a></li><li><a href="#Gatling_and_JMeter_Similarities"><span class="toc_number toc_depth_1">5</span> Gatling and JMeter Similarities</a><ul><li><a href="#Opensource"><span class="toc_number toc_depth_2">5.1</span> Opensource</a></li><li><a href="#Protocol_support"><span class="toc_number toc_depth_2">5.2</span> Protocol support</a></li><li><a href="#IDE_for_Scripting"><span class="toc_number toc_depth_2">5.3</span> IDE for Scripting</a></li><li><a href="#Execution_Report"><span class="toc_number toc_depth_2">5.4</span> Execution Report</a></li><li><a href="#Cloud_Service_Integration"><span class="toc_number toc_depth_2">5.5</span> Cloud Service Integration</a></li><li><a href="#Live_test_run_monitoring"><span class="toc_number toc_depth_2">5.6</span> Live test run monitoring</a></li><li><a href="#DevOps_Support"><span class="toc_number toc_depth_2">5.7</span> DevOps Support</a></li><li><a href="#CLI_Mode"><span class="toc_number toc_depth_2">5.8</span> CLI Mode</a></li></ul></li><li><a href="#Gatling_vs_JMeter_Key_Differences"><span class="toc_number toc_depth_1">6</span> Gatling vs. JMeter: Key Differences</a></li><li><a href="#JMeter_or_Gatling_which_is_better"><span class="toc_number toc_depth_1">7</span> JMeter or Gatling, which is better?</a></li><li><a href="#Conclusion_Gatling_vs_JMeter"><span class="toc_number toc_depth_1">8</span> Conclusion – Gatling vs JMeter</a></li><li><a href="#Frequently_asked_questions"><span class="toc_number toc_depth_1">9</span> Frequently asked questions</a><ul><li><a href="#Is_Gatling_good_for_performance_testing"><span class="toc_number toc_depth_2">9.1</span> Is Gatling good for performance testing?</a></li><li><a href="#Why_is_Apache_JMeter_Getting_More_Popular_than_LoadRunner"><span class="toc_number toc_depth_2">9.2</span> Why is Apache JMeter Getting More Popular than LoadRunner?</a></li></ul></li></ul></div>
<h2 id="h-why-performance-testing"><span id="Why_Performance_Testing"><strong>Why Performance Testing?</strong></span></h2>



<p><a href="https://testsigma.com/blog/performance-testing/">Performance Testing</a> is an evaluation of the system in terms of responsiveness, and stability under expected and unexpected loads. Performance testing focuses on simulating multiple users at the same time&nbsp;</p>



<p>Performance testing cannot be carried out manually, it requires the aid of tools. There are many tools in the market such as K6, Gatling, JMeter, etc. These tools simulate multiple users and record their behavior. The JMeter and Gatling are most popular in this space. Let&#8217;s understand them in detail.</p>



<h2 id="h-what-is-gatling"><span id="What_is_Gatling"><strong>What is Gatling?</strong></span></h2>



<p>Gatling is a load testing tool, built using the Scala language. It supports most of the modern protocols. Gatling uses comparatively fewer resources.&nbsp; Gatling is available as an enterprise tool and as an open-source tool. The commercial version of Gatling offers more functionality for generating load and reporting.</p>



<h2 id="h-what-is-apache-jmeter"><span id="What_is_Apache_JMeter"><strong>What is Apache JMeter?</strong></span></h2>



<p>Apache JMeter is a pure open-source performance testing tool. It comes with a rich IDE. Also supports record and playback, drag and drop support, and scripting with different languages.&nbsp;</p>



<p>JMeter has a huge community base so it is easy to resolve the bottlenecks. JMeter can be used with Blazemeter if you don&#8217;t like to maintain infrastructure. JMeter is most popular due to its simplicity and user-friendliness.</p>



<h2 id="h-gatling-vs-jmeter-detailed-comparison"><span id="Gatling_vs_JMeter_Detailed_Comparison"><strong>Gatling vs JMeter: Detailed Comparison</strong></span></h2>



<p>Gatling and JMeter both are the most popular tools for performance testing. As we know each and every tool has pros and cons. In this section, we are comparing Gatling and JMeter to provide better clarity. This also helps to choose the right performance tool for your organization.</p>



<figure class="wp-block-table"><table><tbody><tr><td><strong>The basis of comparison&nbsp;</strong></td><td><strong>Gatling&nbsp;</strong></td><td><strong>JMeter</strong></td></tr><tr><td><strong>Definition</strong></td><td>Gatling is a performance testing tool. It is available in both open-source and enterprise editions. Gatling supports Scala, Java, and Kotlin languages</td><td>JMeter is a pure open-source performance testing tool. JMeter is developed and managed by the open source community members. JMeter supports both scripting and non-scripting types of performance testing.</td></tr><tr><td><strong>License</strong></td><td>Open source (Apache 2.0) and Commercial License</td><td>Open source Apache 2.0</td></tr><tr><td><strong>CI/CD Integration</strong></td><td>Gatling provides out-of-the-box support for CI/CD integration. It can be integrated into Jenkins, Bamboo, and TeamCity.</td><td>JMeter supports CI/CD Integration. However, the option is not out of the box. You need to do some configurations to integrate CI/CD Systems</td></tr><tr><td><strong>Developed with</strong></td><td>Built with Scala, Akka, and Netty</td><td>Built with Java</td></tr><tr><td><strong>Generality</strong></td><td>CLI tool, Reporting, Dashboard, and Real-time monitoring.</td><td>Supports CLI execution, reporting however doesn&#8217;t support out-of-the-box real-time monitoring</td></tr><tr><td><strong>Maintenance</strong></td><td>Gatling Enterprise</td><td>Apache software foundation/ Open Source community members</td></tr><tr><td><strong>Built-in Facilities</strong></td><td>Supports CI/CD integrations, Reporting, Dashboard, CLI Execution</td><td>Supports UI-based test execution, Drag and drop support, Reporting, CLI Execution</td></tr><tr><td><strong>Ease of Use</strong></td><td>Requires programming skills to use</td><td>It requires minimal technical knowledge to use</td></tr><tr><td><strong>Protocol Support</strong></td><td>Supports HTTP, FTP, TCP, JDBC, JMS etc.</td><td>Supports HTTP, HTTPS, JMS, etc.</td></tr><tr><td><strong>Real-Time Test Monitoring</strong></td><td>Yes</td><td>Support is not out of the box, need to configure third-party plugins</td></tr><tr><td><strong>Plugins</strong></td><td>Fewer third-party plugins are available.</td><td>As it is community-driven, a massive number of plugins are available to use</td></tr><tr><td><strong>Third-party script recorder availability</strong></td><td>Doesn&#8217;t support third-party script recorder</td><td>Supports third-party script recorders.</td></tr><tr><td><strong>Source control supports</strong></td><td>Gatling tests that are saved as code, so it is easy to use source control tools such as Git, Bitbucket, etc.</td><td>JMeter stores files in .jmx format; it doesn&#8217;t fit well with source control tools.</td></tr><tr><td><strong>Test Execution</strong></td><td>CLI</td><td>Server mode, CLI and GUI</td></tr></tbody></table></figure>



<h2 id="h-gatling-and-jmeter-similarities"><span id="Gatling_and_JMeter_Similarities"><strong>Gatling and JMeter Similarities</strong></span></h2>



<h3 id="h-opensource"><span id="Opensource"><strong>Opensource</strong></span></h3>



<p>JMeter and Gatling both are available as open source. JMeter is purely community driven so it offers only an open source version. Whereas, Gatling provides additional features with a commercial version. However, the open-source version should fit your basic needs.</p>



<h3 id="h-protocol-support"><span id="Protocol_support"><strong>Protocol support</strong></span></h3>



<p>Both tools support modern protocols such as HTTP, HTTPS, DB Testing, and JMS.</p>



<h3 id="h-ide-for-scripting"><span id="IDE_for_Scripting"><strong>IDE for Scripting</strong></span></h3>



<p>The JMeter has a rich UI interface with drag-and-drop support. Gatling also introduced the feature-rich UI to make the scripting faster. So, the IDE is available in both tools.</p>



<h3 id="h-execution-report"><span id="Execution_Report"><strong>Execution Report</strong></span></h3>



<p>The JMeter offers different types of reports, HTML, text-based reports, etc. Gatling offers HTML reports by default. However, with advanced versions, different reports are possible.</p>



<h3 id="h-cloud-service-integration"><span id="Cloud_Service_Integration"><strong>Cloud Service Integration</strong></span></h3>



<p>There are cloud service partners like Blazemeter, which help to reduce the infrastructure burden. Both tools support cloud service integration.</p>



<h3 id="h-live-test-run-monitoring"><span id="Live_test_run_monitoring"><strong>Live test run monitoring</strong></span></h3>



<p>The JMeter offers live test monitoring with third-party plugins. The Gatling advanced version supports live test monitoring.</p>



<h3 id="h-devops-support"><span id="DevOps_Support"><strong>DevOps Support</strong></span></h3>



<p>Though the JMeter was not built for CI/CD, it supports almost all different types of DevOps tools however, some configuration is required. The Gatling supports CI/CD integration with less configuration as it is built with DevOps support in mind.&nbsp;</p>



<h3 id="h-cli-mode"><span id="CLI_Mode"><strong>CLI Mode</strong></span></h3>



<p>Both JMeter and Gatling Support CLI mode, but the JMeter supports additional test execution types such as UI Mode and Server mode.</p>



<h2 id="h-gatling-vs-jmeter-key-differences"><span id="Gatling_vs_JMeter_Key_Differences"><strong>Gatling vs. JMeter: Key Differences</strong></span></h2>



<ul><li><strong>UI:</strong> JMeter provides a rich UI with all possibilities of customization, whereas the Gatling UI is basic, and listeners are not supported. While analyzing the performance bottlenecks it is difficult without result listeners</li><li><strong>Scripting:</strong> JMeter supports UI-based drag and drop, as well as different programming languages such as Groovy, Beanshell, etc. The Gatling supports Scala, Kotlin, and Java</li><li><strong>File format:</strong> JMeter saves the file in .jmx which is a customized XML format, with this it is difficult to integrate with the source control and perform the reviews. The Gatling saves the script in programming language format so it is easy to integrate with the source control tools.</li><li><strong>Cloud Service provider:</strong> The JMeter is supported by almost all modern cloud service providers however the cloud service provider for the Gatling is limited.</li><li><strong>Test Execution: </strong>The JMeter test can be executed with Server mode, UI mode, and command line mode. The Gatling supports only CLI mode.</li><li><strong>Reports and Customizations: </strong>JMeter is an open source that supports all possible customization. Reports can be tweaked as per organization requirements. The Gatling supports reports, but customization is very limited.</li><li><strong>User-friendliness</strong>: The JMeter offers a rich UI, but the UI mode is resource heavy. Users are facing performance issues with JMeter. The JMeter UI consumes a lot of resources. The Gatling feels lighter while using, and the resource is optimized well.</li></ul>



<h2 id="h-jmeter-or-gatling-which-is-better"><span id="JMeter_or_Gatling_which_is_better"><strong>JMeter or Gatling, which is better?</strong></span></h2>



<p>As we discussed above, both the tools have pros and cons. The better tool needs to be selected based on the organization&#8217;s requirements. Gatling offers an enterprise version that is bundled with all different features and is easy to use. However, you need to pay for the license. The JMeter comes free, it is more flexible and customizable, but it requires technical knowledge for advanced scripting.</p>



<p><br><p><button class="btn bg-primary cta-btn" style="margin: auto"><a href="https://testsigma.com/automated-testing" target="_blank" rel="noopener noreferrer" style="color:#fff">Learn about Automated Testing in general</a></button></p><br></p>



<h2 id="h-conclusion-gatling-vs-jmeter"><span id="Conclusion_Gatling_vs_JMeter"><strong>Conclusion – Gatling vs JMeter</strong></span></h2>



<p>Performance testing is a crucial part of testing web applications. A performance testing tool plays a key role in providing the desired outcome. Both JMeter and Gatling are popular in the market. JMeter is easy to use for basic performance testing, the advanced scripting requires good technical skills. Gatling provides both open-source versions and commercial versions. The functionality of the open-source version is limited. Though the commercial version offers more rich features it adds cost overhead to the organization. Considering the cost and cloud service providers &#8211; most organizations choose JMeter. However, you need to consider the cost, upskilling resources, infrastructure maintenance, cloud integration, and other organization requirements while choosing the best performance tool.</p>



<h2 id="h-frequently-asked-questions"><span id="Frequently_asked_questions"><strong>Frequently asked questions</strong></span></h2>



<h3 id="h-is-gatling-good-for-performance-testing"><span id="Is_Gatling_good_for_performance_testing"><strong>Is Gatling good for performance testing?</strong></span></h3>



<p>Gatling is a good performance testing tool, it closely competes with JMeter. The commercial version of Gatling is more capable and easy to use. Furthermore, Gatling uses modern tech stacks which helps to provide accurate results.</p>



<h3 id="h-why-is-apache-jmeter-getting-more-popular-than-loadrunner"><span id="Why_is_Apache_JMeter_Getting_More_Popular_than_LoadRunner"><strong>Why is Apache JMeter Getting More Popular than LoadRunner?</strong></span></h3>



<p>Apache JMeter is open source and it offers a lot of customizations. The documentation is very clear. It also offers a lot of community plugins which help to customize the performance testing tool the way the organization wants. The LoadRunner is a proprietary tool by Micro Focus; though it offers rich features, the licensing cost is an additional overhead.</p>


Gatling vs JMeter: Top 10 Key Differences

What are the Test Scenarios for Flipkart Application?


<p>Writing test cases manually or through automation for a calendar involves understanding the calendar application requirements or acceptance criteria and business objectives. Additionally, you’ll want to consider usability and accessibility. After all, calendars are handy tools for everyone using a computer or other device.&nbsp;&nbsp;</p>



<p>Use requirements or even a mind map, or outline to begin separating individual test scenarios. Once you’ve gathered a checklist of test objectives you’re ready to get started writing quality test cases for calendars.&nbsp;</p>



<div id="toc_container" class="no_bullets"><p class="toc_title">Table Of Contents</p><ul class="toc_list"><ul><li><a href="#Calendar_Test_Cases"><span class="toc_number toc_depth_2">0.1</span> Calendar Test Cases</a></li><li><a href="#High-Level_Test_Cases_For_Calendar_Application"><span class="toc_number toc_depth_2">0.2</span> High-Level Test Cases For Calendar Application</a></li><li><a href="#Positive_Test_Cases_for_Date_Field"><span class="toc_number toc_depth_2">0.3</span> Positive Test Cases for Date Field</a></li><li><a href="#Negative_Test_Cases_for_Date_Field"><span class="toc_number toc_depth_2">0.4</span> Negative Test Cases for Date Field</a></li></ul></li><li><a href="#How_To_Write_Test_Cases_For_Calendar_Requirements"><span class="toc_number toc_depth_1">1</span> How To Write Test Cases For Calendar? (Requirements )</a></li><li><a href="#How_to_Automate_Calendar_Test_Cases_with_Testsigma"><span class="toc_number toc_depth_1">2</span> How to Automate Calendar Test Cases with Testsigma?</a></li><li><a href="#Conclusion"><span class="toc_number toc_depth_1">3</span> Conclusion</a></li><li><a href="#Frequently_Asked_Questions"><span class="toc_number toc_depth_1">4</span> Frequently Asked Questions</a><ul><li><a href="#How_to_test_a_date_picker_in_manual_testing"><span class="toc_number toc_depth_2">4.1</span> How to test a date picker in manual testing?</a></li><li><a href="#How_do_I_automate_a_calendar_in_Selenium_WebDriver_for_automation_testing"><span class="toc_number toc_depth_2">4.2</span> How do I automate a calendar in Selenium WebDriver for automation testing?</a></li><li><a href="#Examples_of_test_cases_for_calendar"><span class="toc_number toc_depth_2">4.3</span> Examples of test cases for calendar?</a></li></ul></li></ul></div>
<h3 id="calendar-test-cases"><span id="Calendar_Test_Cases"><strong>Calendar Test Cases</strong></span></h3>



<p>Calendar test cases can vary between calendar applications. It’s important for test validity to ensure you create a test case for each major functional scenario for your calendar application. Start by determining whether your test objectives fit as high-level, positive, or negative test cases. Leverage information in requirements, acceptance criteria, and testing standards to determine each test and where it fits. Write a test case for calendar applications that ensure a positive customer experience.&nbsp;</p>



<h3 id="high-level-test-cases-for-calendar-application"><span id="High-Level_Test_Cases_For_Calendar_Application"><strong>High-Level Test Cases For Calendar Application</strong></span></h3>



<ul><li>The app opens and displays essential features including month, day, and year in a standard calendar format.&nbsp;</li><li>Write test cases for calendars where users can switch between months.&nbsp;</li><li>Users should be able to switch between years.&nbsp;</li><li>Users should be able to click on a specific day.&nbsp;</li><li>Users should be able to click on a day and add an event.&nbsp;</li></ul>



<h3 id="positive-test-cases-for-date-field"><span id="Positive_Test_Cases_for_Date_Field"><strong>Positive Test Cases for Date Field</strong></span></h3>



<ul><li>Enter a valid date in the expected format directly into the date field.&nbsp;</li><li>Users can open an added event on one date and directly change the date to a new, valid date.&nbsp;</li><li>Click to choose a valid date from a calendar selector tool in the same year.&nbsp;</li><li>Click to change the year and choose a valid date from a calendar selector tool.&nbsp;</li><li>Include a test case for the calendar app that includes entering a valid date in the past.&nbsp;</li><li>Enter a valid date in the future.&nbsp;</li></ul>



<h3 id="negative-test-cases-for-date-field"><span id="Negative_Test_Cases_for_Date_Field"><strong>Negative Test Cases for Date Field</strong></span></h3>



<ul><li>A date entered in an invalid format (YYMMDD, DDYYMM for example).&nbsp;</li><li>Enter a date with extra characters (12//12//2023 for example).&nbsp;</li><li>Enter a date with alpha characters (invalid data for example: 12/AB/CD).</li><li>Enter a date without the / characters, assuming the / character is valid.&nbsp;</li><li>Enter a date that does not exist (12/32/2023 or 11/00/2023).</li></ul>



<h2 id="how-to-write-test-cases-for-calendar-requirements"><span id="How_To_Write_Test_Cases_For_Calendar_Requirements"><strong>How To Write Test Cases For Calendar? (Requirements )</strong></span></h2>



<ul><li>Follow test case writing best practices by following a <a href="https://testsigma.com/blog/test-case-template/" target="_blank" rel="noreferrer noopener">test case template</a>, or creating one that meets your QA team’s requirements.&nbsp;</li><li>Use a plain language format to outline each required test case objective.&nbsp;</li><li>Create tests in a modular design to facilitate test automation for end-to-end tests.&nbsp;</li><li>Ensure each requirement or acceptance criteria is covered with at least one test case.&nbsp;</li><li>Design test cases for calendars that cover the expected user workflow for the calendar in full.&nbsp;</li></ul>



<div class="cta-banner-v2">
<div class="title-with-description ">
<p class="title">Run your web app tests on 3000+ real devices and browsers on the cloud</p>
</div>
<a href="https://testsigma.com/signup" target="_blank" class="cta-btn-v1" rel="noopener">Signup for free</a>
</div>



<h2 id="how-to-automate-calendar-test-cases-with-testsigma"><span id="How_to_Automate_Calendar_Test_Cases_with_Testsigma"><strong>How to Automate Calendar Test Cases with Testsigma?</strong></span></h2>



<ul><li>Write scripts in plain English similar to a manual test case.&nbsp;</li><li>Record the steps you take within the calendar app and generate automated tests at the click of a button.&nbsp;</li><li>Once tests are written create an execution schedule.&nbsp;</li><li>Start by executing the test locally on the preferred browser.&nbsp;</li><li>Execute tests across supported browsers in the Testsigma system.&nbsp;</li><li>Execute tests on various supported devices within the Testsigma system.&nbsp;</li></ul>



<p>Sample Testsigman plain English script:</p>



<div class="wp-block-image"><figure class="aligncenter size-full"><img loading="lazy" width="512" height="266" src="https://s3.amazonaws.com/blog-assets-production.testsigma.com/blogs/wp-content/uploads/2024/01/11171524/Automate-calendar-app-tests-with-Testsigma-.png" alt="Automate Calendar Test Cases with Testsigma" class="wp-image-54565"/></figure></div>



<div class="cta-banner-v2">
<div class="title-with-description ">
<p class="title">Automate Calendar Apps easily using Testsigma’s codeless test automation</p>
</div>
<a href="https://testsigma.com/signup" target="_blank" class="cta-btn-v1" rel="noopener">Sign up for Free</a>
</div>



<h2 id="conclusion"><span id="Conclusion"><strong>Conclusion</strong></span></h2>



<p>Careful planning and attention to detail are critical when writing valid, useful test cases that can be reused. Whether tests are written manually or developed with test automation, make sure the scripts are clearly written and accurate.&nbsp;</p>



<p>Consider using a test case template for either manual or test automation to ensure every test case has the necessary information for tracking execution status and any identified defects.&nbsp;</p>



<h2 id="frequently-asked-questions"><span id="Frequently_Asked_Questions"><strong>Frequently Asked Questions</strong></span></h2>



<h3 id="how-to-test-a-date-picker-in-manual-testing"><span id="How_to_test_a_date_picker_in_manual_testing"><strong>How to test a date picker in manual testing?</strong></span></h3>



<p>Create both positive and negative tests for the expected requirements. Ensure valid date formats function without error. Additionally, test negative test scenarios including invalid date formats, dates that don’t exist, and invalid character entry. Most calendar apps use a variety of date formats based on country. Test every valid option and configuration settings for each to ensure each option works as expected.&nbsp;</p>



<h3 id="how-do-i-automate-a-calendar-in-selenium-webdriver-for-automation-testing"><span id="How_do_I_automate_a_calendar_in_Selenium_WebDriver_for_automation_testing"><strong>How do I automate a calendar in Selenium WebDriver for automation testing?</strong></span></h3>



<p>Start by creating an outline of test objectives. Create a test using Selenium WebDriver for each test objective you need to verify. Like most automated testing tools, Selenium requires the ability to identify objects by ID in the code. Check with development or review the code to ensure IDs are in place for all calendar fields. Once you have all the information you need, choose to record the test with Selenium or create tests yourself with easy scripting tools. <a href="https://www.quora.com/How-do-I-automate-a-calendar-in-Selenium-WebDriver-for-automation-testing" target="_blank" rel="noreferrer noopener">Find out more </a>here.&nbsp;</p>



<h3 id="h-examples-of-test-cases-for-calendar"><span id="Examples_of_test_cases_for_calendar"><strong>Examples of test cases for calendar?</strong></span></h3>



<ul><li>The app opens and displays essential features including month, day, and year in a standard calendar format.&nbsp;</li><li>Users can switch between months.&nbsp;</li><li>Users can switch between years.&nbsp;</li><li>Users can click on a specific day.&nbsp;</li><li>Users can click on a day and add an event.&nbsp;</li></ul>



<ul><li>Enter a valid date in the expected format directly into the date field.&nbsp;</li><li>Users can open an added event on one date and directly change the date to a new, valid date.&nbsp;</li><li>Select an event and edit the date field directly.&nbsp;</li><li>Select an event and edit the date by choosing a date with a calendar selector tool.&nbsp;</li><li>Save changes and then reopen events and verify changes are saved without error.</li></ul>


Calendar Test Cases How to Write (Samples)

Calendar Test Cases | How to Write? (Samples)

Ionic Testing What, Why it Matters and How to Perform

Ionic Testing | What, Why it Matters and How to Perform?

How to do Deep Link Testing on Android & iOS devices?

How Do You Write Test Cases for Game Testing

How Do You Write Test Cases for Game Testing?

Test Automation Projects What, Types, and Best Practices

Test Automation Projects | What, Types, and Best Practices


<p>Most QA pipelines must necessarily include, among other test types, exploratory testing. However, adequately comprehensive exploratory testing requires a certain measure of planning and organization – testing objectives, the features to “explore” in the test, expected results, how to record the actual results, and more.&nbsp;</p>



<p>All this information needs to be streamlined into a singular, self-explanatory document, accessible and understandable to the right people. In the QA ecosystem, this document is called a test charter.&nbsp;</p>



<p>In this article, we’ll dive into the definition, nature, benefits, format, and usage of test charters. Think of this as your first step into understanding and creating project-optimal test charters.&nbsp;</p>



<div id="toc_container" class="no_bullets"><p class="toc_title">Table Of Contents</p><ul class="toc_list"><li><a href="#What_is_a_Test_Charter"><span class="toc_number toc_depth_1">1</span> What is a Test Charter?</a></li><li><a href="#Why_do_we_need_a_test_charter"><span class="toc_number toc_depth_1">2</span> Why do we need a test charter?</a></li><li><a href="#Benefits_of_Test_Charters"><span class="toc_number toc_depth_1">3</span> Benefits of Test Charters</a><ul><li><a href="#How_to_Develop_a_Test_Charter"><span class="toc_number toc_depth_2">3.1</span> How to Develop a Test Charter</a></li></ul></li><li><a href="#Test_Charter_Format_Free_Template"><span class="toc_number toc_depth_1">4</span> Test Charter Format (Free Template)</a></li><li><a href="#Conclusion"><span class="toc_number toc_depth_1">5</span> Conclusion</a></li><li><a href="#Frequently_Asked_Questions"><span class="toc_number toc_depth_1">6</span> Frequently Asked Questions</a><ul><li><a href="#What_is_an_exploratory_test_charter"><span class="toc_number toc_depth_2">6.1</span> What is an exploratory test charter?</a></li></ul></li></ul></div>
<h2 id="h-what-is-a-test-charter"><span id="What_is_a_Test_Charter">What is a Test Charter?</span></h2>



<p>Test charter refers to a document providing an overview of the parameters, goals, and plans governing a test session. It includes information defining the feature under test, the premise/query, the required tool, possible risks, data dependencies, and expected results as well as deadlines.&nbsp;</p>



<p>At a high-level, it is a manual for <a href="https://testsigma.com/blog/exploratory-testing/" target="_blank" rel="noreferrer noopener">exploratory testing</a> sessions. It answers questions such as:</p>



<ul><li>What is the primary goal of this test session?</li><li>How long is the test session?</li><li>Which feature(s) will be tested in this session?</li><li>What tools are required for this test session?</li><li>What are the expected results of the test?</li><li>What are the user expectations and requirements for this feature?</li><li>How do I record the actual results?</li><li>Who do I report the results to, once the test is completed?</li></ul>



<p>It is best to assign one test charter to a single session. This helps isolate features when testing and recording results. It also ensures that testers can focus on a single feature, and really get into its systematic operations to verify functionality.&nbsp;</p>



<h2 id="h-why-do-we-need-a-test-charter"><span id="Why_do_we_need_a_test_charter">Why do we need a test charter?</span></h2>



<p>Simply put, we need a test charter because exploratory testing does not follow predefined steps. It also does not come with “expected results&#8221; set in stone. This is because the point of the test is to “explore”; testers literally explore the software with the intent to come across any bugs within each feature.&nbsp;</p>



<p><strong>Note</strong>: Exploratory testing is usually not part of <a href="https://testsigma.com/automated-testing" target="_blank" rel="noreferrer noopener">test automation</a> suites. It requires human judgment, and must necessarily be manually tested. </p>



<br><p><button class="btn bg-primary cta-btn" style="margin: auto"><a href="https://testsigma.com/automated-testing" target="_blank" rel="noopener noreferrer" style="color:#fff">Learn more about test automation</a></button></p><br>



<p>Now, this does not mean that testers “explore” the system randomly. They are chosen for their experience, so they know what to look for, and how users would navigate an app or page. They are also given detailed information about requirements, user expectations, and the software’s main functions – all included in the test charter.&nbsp;</p>



<p>The charter helps testers stay focused during exploratory sessions. By designating a single feature and laying out our user expectations, the test charter ensures that QAs do not get bogged down in unnecessary details. They don’t end up testing irrelevant components or verifying aspects that end-users don’t care about (at this stage of testing).</p>



<p>Despite providing a guiding principle, good test charters also encourage diverse and creative thinking. They don’t tell QAs what to test, but give them the core values for the session. QAs keep the primary variable (user expectations, software design) as the base of their action, and then use their industry experience to replicate common and uncommon user scenarios.&nbsp;</p>



<p>Since test charters don’t restrict testers’ actions, they lead to more interesting and experimental test scenarios. That is always a good thing because it generates innovative thinking.&nbsp;</p>



<h2 id="h-benefits-of-test-charters"><span id="Benefits_of_Test_Charters">Benefits of Test Charters</span></h2>



<ul><li><strong>Facilitates continuous learning</strong>: Test charters provide an organized framework for test design, and execution, as well as for interpreting results and extracting accurate learnings. While exploratory testing is always left to the tester’s volition (they decide how to use a certain feature, without predetermined test steps).<br><br>However, the test charter provides them with relevant information to better guide the testers’ efforts. An important part of that is evaluating the right variables and identifying opportunities for improvement, be it for the software or the testing process.<br><br>Test charters streamline exploratory testing without limiting the testers’ autonomy.<br></li><li><strong>Assists with innovation and sharing knowledge</strong>: Test charters provide structure, direction, and a central repository for every tester to add their conclusions. As is well known, agile development and testing flourish best when individual members and teams collaborate.<br><br>Test charters provide sufficient context for such collaboration. They record the intent and duration of each session, enabling quicker feedback cycles and analysis.  These charters provide the framework for testers to apply their domain knowledge, intuition, analysis, and user-first thinking.<br></li><li><strong>Helps find bugs not predicted in other tests</strong>: Since exploratory testing is unplanned in execution, it reveals bugs that other planned tests do not. With no test scripts, exploratory testers are free to literally do anything they want on a certain software application. Unpredictable user actions will automatically increase the likelihood of finding bugs no one expected when creating test cases and scripts.<br><br>By directing and structuring exploratory testing, test charters expand test coverage, extending it to the blind spots of other tests. It provides a significant failsafe mechanism for all <a href="https://testsigma.com/guides/software-testing/" target="_blank" rel="noreferrer noopener">software testing</a> projects. </li></ul>



<h3 id="h-how-to-develop-a-test-charter"><span id="How_to_Develop_a_Test_Charter">How to Develop a Test Charter</span></h3>



<p>The key to developing an effective test charter is to be methodical. Break down the process into steps using an outline focused on software requirements and projected user preferences. Additionally, be aware that all elements of the test charter will change as the project and software under development evolve.&nbsp;</p>



<ul><li>Start by isolating the feature to be tested.&nbsp;</li><li>Note down all relevant project specifications, user stories, risk assessment, and technical as well as business requirements.&nbsp;</li><li>Create the “test idea” i.e., the idea around which the test will proceed. This is up to the QA, who will create it using their experience and intuition.&nbsp;</li><li>Detail the resources, data, tools, and environment requirements for the test.&nbsp;</li><li>Mention the goals of the test session.&nbsp;</li><li>Highlight the expected results.&nbsp;</li><li>Describe the process for noting results (whether to take screenshots, record video, etc.)</li><li>Finally, state possible obstacles that may be encountered during the test. These hazards can be estimated reasonably accurately by experienced testers who understand the product end-to-end.&nbsp;</li></ul>



<h2 id="h-test-charter-format-free-template"><span id="Test_Charter_Format_Free_Template">Test Charter Format (Free Template)</span></h2>



<p>At a high level, every test charter should include the following variables:</p>



<ul><li><strong>Name</strong>: The charter name should describe the test in question. For example, “Profile creation for new users on &lt;application name&gt; or “Testing review mechanisms (leaving comments, star or number reviews)”.<br><br>The idea is to describe the purpose of the test charter upfront so that anyone else viewing this document immediately knows its purpose and content.<br><br>“Quick attacks around profile creation” or “Test multi-user comments, permissions, and race conditions within and out of group membership.”<br></li><li><strong>Test area:</strong> Mention and describe the feature to be tested. Additionally, describe the test harness used in the session.<br></li><li><strong>Date and time</strong>: Mention the date and time of the test’s starting.<br></li><li><strong>Tester’s Name</strong>: Self-explanatory.<br></li><li><strong>Task Breakdown:</strong> The tester describes, as an overview, the direction of the test and steps to be taken within the session.<br></li><li><strong>Duration</strong>: How long will the test take or is expected to take?<br></li><li><strong>Test Design &amp; Execution</strong>: This section should comprise information about how the actual test is conducted, and what steps the tester actually took. This can be filled in detail after the test is completed (since exploratory tests are unplanned).<br><br>Simply describe the actions taken during the test. Don’t forget to include the observations gathered during said test.<br></li><li><strong>Bug reports</strong>: Describe the bugs found, the nature of each, at what point in the test they showed up, and what anomalies are showing up with each bug and steps to reproduce them. This would largely be information about bugs captured through screen recording, screenshots, text logs, etc.<br><br>For convenience’s sake, number or name each bug.<br></li><li><strong>Session setup</strong>: Detail the tools, test data, and test environment to be prepped before the test begins.<br></li><li><strong>Charter vs. Opportunity</strong>: This is the &amp; of time the tester spends on the expected system features as opposed to unexpected parts of the system under test.&nbsp;<br></li><li><strong>Expected Results</strong>: What is the test expected to achieve? What are the ideal results?<br></li><li><strong>Actual Results</strong>: Self-explanatory.&nbsp;</li></ul>



<p><strong>Here is the link to  a downloadable charter: </strong><a href="https://www.tmap.net/sites/tmap/files/2019-08/Template%20Exploratory%20testing%20charter%20Simple%20v1.docx" target="_blank" rel="noreferrer noopener nofollow"><strong>https://www.tmap.net/sites/tmap/files/2019-08/Template%20Exploratory%20testing%20charter%20Simple%20v1.docx</strong></a><strong> </strong></p>



<h2 id="h-conclusion"><span id="Conclusion">Conclusion</span></h2>



<p>Test charters turn exploratory tests into a science and art. They provide direction without hampering creativity, so testers and projects get the best of both worlds. They are essential to rein in the unplanned nature of exploratory testing, and thus keep them on track (there is a real danger of the tester getting lost in exploring features beyond immediate requirements).&nbsp;</p>



<p>Use this article to create your first test charter. As you keep building more tests and corresponding charters, it will become simpler to predict and understand the needs of the team, customers, and other stakeholders. Consequently, creating mature, targeted test charters will be a simple task.&nbsp;</p>



<h2 id="h-frequently-asked-questions"><span id="Frequently_Asked_Questions">Frequently Asked Questions</span></h2>



<h3 id="h-what-is-an-exploratory-test-charter"><span id="What_is_an_exploratory_test_charter">What is an exploratory test charter?</span></h3>



<p>An exploratory test charter is a document that details all the parameters, goals, and plans governing an exploratory test session. It mentions and discusses the feature under test, the premise/query, the required tool, possible risks, data dependencies, and expected results as well as deadlines.</p>


What is a Test Charter Why Use It & How to Write One