ACCELQ vs Tosca – Which One You Should Choose?


<p>Testing mobile phone number fields sounds simple and it is, but it can be complex if multiple locations (countries) are supported. Phone number formats are often different depending on the country or nation. Supported locations make a difference when testing phone number formats, number entry patterns, and error messaging based on type and location.</p>



<p><a href="https://testsigma.com/guides/what-is-test-case/" target="_blank" rel="noreferrer noopener">Test cases</a> for mobile numbers vary based on a user&#8217;s global location (country). The application design or requirements are likely based on a specific location or multiple locations. If your documentation doesn’t specify, ask the product manager, designer, or developer for all supported locations to test against.&nbsp;</p>



<p></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_Mobile_Number_Field"><span class="toc_number toc_depth_1">1</span> What is a Mobile Number Field</a></li><li><a href="#Test_Cases_For_the_Mobile_Number_Field"><span class="toc_number toc_depth_1">2</span> Test Cases For the Mobile Number Field</a></li><li><a href="#Manual_and_Automatednbsp"><span class="toc_number toc_depth_1">3</span> Manual and Automated&nbsp;</a></li><li><a href="#Summary"><span class="toc_number toc_depth_1">4</span> Summary</a></li><li><a href="#Frequently_Asked_Questions"><span class="toc_number toc_depth_1">5</span> Frequently Asked Questions</a><ul><li><a href="#What_are_the_negative_test_cases_for_the_phone_number_field"><span class="toc_number toc_depth_2">5.1</span> What are the negative test cases for the phone number field?</a></li></ul></li></ul></div>
<h2 id="h-what-is-a-mobile-number-field"><span id="What_is_a_Mobile_Number_Field"><strong>What is a Mobile Number Field</strong></span></h2>



<p>A mobile number field is a representation of a user’s phone number. The format, style, and characters accepted change based on specific application requirements and whether the application is using the E.164 (The International Public Telecommunication Numbering Plan) standard and/or the NANP (North American Numbering Plan).&nbsp;</p>



<p>Test cases for mobile phones need to consider both the <a href="https://learn.microsoft.com/en-us/globalization/locale/telephone-numbers" target="_blank" rel="noreferrer noopener">E.164 and NANP</a> if the application is sold globally. The E.164 sets a number limit of 15 characters including a three-digit country code. All nations using the NANP have a country code of 1 and a ten-digit number character limit. The first set of numbers represent the country code followed by the regional code and then the phone number.&nbsp;</p>



<h2 id="test-cases-for-the-mobile-number-field"><span id="Test_Cases_For_the_Mobile_Number_Field"><strong>Test Cases For the Mobile Number Field</strong></span></h2>



<p>Phone number test cases are assumed in this blog to support both the E.164 and the NANP. We’ve listed the valid test cases first, followed by a few suggested tests for negative or error messaging testing.&nbsp;</p>



<p><strong>Mobile number test cases for functional testing include:</strong></p>



<ul><li>Verify the mobile phone field exists and accepts data entry.</li><li>Enter a valid phone format for a specific location (US and other nations)<ul><li>Verify the user must include the country or area code.&nbsp;</li><li>Verify NANP standards apply to the United States, Canada, and Jamaica.</li><li>Verify E-164 standards apply to all other countries.&nbsp;</li><li>Verify any countries that don’t follow the E-164 standard.&nbsp;</li></ul></li><li>Copy and paste a valid number from a different form field.</li><li>If the mobile number field is required, verify there is a visual indicator to let the user know valid data must be entered.</li><li>Depending on the field design, including special characters to separate numbers like parentheses and dashes:<ul><li>Example: (202) 444-9876.</li></ul></li><li>If the application uses drop down selectors, select a valid country and enter a valid number for that location.</li><li>Select the country code dropdown and view the list of supported country formats.&nbsp;<ul><li>Verify the list is in alphabetical order for easier viewing.&nbsp;</li><li>Verify the number selected displays in the field as expected.&nbsp;</li></ul></li><li>Test that the tab order stops in the mobile phone field and allows the user to enter a valid number.&nbsp;</li><li>View the field and check that it aligns as expected with other fields and within a group.&nbsp;</li></ul>



<p><strong>Mobile number negative test cases include:</strong></p>



<ul><li>Exceeding the allowed character limit.</li><li>Entering a correct country or area code with an invalid number for that location.</li><li>Enter an invalid country or area code with a valid number.</li><li>Enter in numeric characters with alpha characters.<ul><li>Example: 1404abc9877.</li></ul></li><li>Enter a valid country code and a phone number that’s one or more numbers to short for the selected location.&nbsp;</li><li>Enter a valid country code and a phone number that exceeds the character limit for the location.</li><li>Enter a valid phone number but include various special characters (!@#$%^&amp;*())<ul><li>Example: 1720(3457)</li><li>Example: 005588#</li></ul></li><li>Enter as many characters as the field allows up to 100.&nbsp;<ul><li>This test sounds silly, but it’s a good way to verify that the application is coded to avoid mass data entry.&nbsp;</li></ul></li><li>Enter a scripted SQL or HTML coded string.&nbsp;<ul><li>This test checks that the field does not execute code.&nbsp;</li><li>Example: 18084560&lt;bold&gt;97&lt;/bold&gt;</li></ul></li><li>If the mobile phone field is required, try to enter and save information without filling it in.&nbsp;<ul><li>Optionally, try filling the mobile phone field with invalid data or partial valid numbers.&nbsp;</li></ul></li></ul>



<p>For each negative test case, verify an error message is triggered indicating the error so the user can understand the problem and make corrections. Remember it’s good practice to have a peer or developer to <a href="https://testsigma.com/blog/test-case-review/" target="_blank" rel="noreferrer noopener">review test cases</a> when possible. The better the test case, the better the test coverage.&nbsp;</p>



<h2 id="manual-and-automated"><span id="Manual_and_Automatednbsp"><strong>Manual and Automated&nbsp;</strong></span></h2>



<p>The table below gives you an example of typical test scenarios for creating manual test cases for mobile numbers:</p>



<figure class="wp-block-table"><table><tbody><tr><td><strong>Test ID</strong></td><td><strong>Description</strong></td><td><strong>Expected Result</strong></td></tr><tr><td>1</td><td>Verify the mobile phone field exists and accepts data entry.</td><td>Confirm the field exists and is enabled to allow users to enter data.&nbsp;</td></tr><tr><td>2</td><td>Enter a valid phone format for each specific location format supported.&nbsp;</td><td>Verify each supported format allows users to enter a valid phone number into the field without resulting in an error.&nbsp;</td></tr><tr><td>3</td><td>If the application uses drop down selectors, select a valid country and enter a valid number for that location.</td><td>Select each drop down option in turn and verify it matches with a valid phone number.&nbsp;Confirm no error messages are generated.&nbsp;</td></tr><tr><td>4</td><td>Test that the tab order stops in the mobile phone field and allows the user to enter a valid number.</td><td>Tab through the form or page fields and verify it lands as expected in the mobile phone field.&nbsp;Enter a valid number and verify no errors are generated.&nbsp;</td></tr></tbody></table></figure>



<p>The above table is a sampling only. You can write as many test cases as you need to cover requirements and standard functionality within your application. Additionally, you can create test cases in a design that fits with your development and QA team.&nbsp;</p>



<p>Creating test cases for mobile phones are excellent candidates for test automation. For creating test cases for mobile phones consider using Low code test automation platform, Testsigma and organize your tests in the following modular flow as below:</p>



<figure class="wp-block-table"><table><tbody><tr><td><strong>Test ID</strong></td><td><strong>Description</strong></td><td><strong>Expected Result</strong></td></tr><tr><td>1</td><td>Click into the mobile phone field.&nbsp;Enter test data for a valid US based phone number: 1+(309)665-9087</td><td>Validate the correct phone number displays and is saved without error.&nbsp;</td></tr><tr><td>2</td><td>Click into the mobile phone field. Enter test data for a valid UK phone number: +44&nbsp; 20 7123 4567<br><strong>NOTE:</strong> Consider using Testsigma’s automation tool to run through all valid formats in a single test. Add validation points for each valid type.&nbsp;</td><td>Validate the correct phone number displays and is saved without error.&nbsp;</td></tr><tr><td>3</td><td>Create a test script that enters all required fields with valid data including the mobile phone field.&nbsp;<br>Click the Save/Submit button when all fields are filled.&nbsp;</td><td>Verify for each supported format type the application enters valid data into the database and saves/submits without error.&nbsp;</td></tr><tr><td>4</td><td>In the application form, enter valid phone numbers for each supported location type but leave off at least one digit.</td><td>Validate each supported format type generates the correct error message.&nbsp;<br>Enter a validation point for each format’s specific error message.&nbsp;</td></tr></tbody></table></figure>



<p>Note, the above is a sample. You can learn how to use Testsigma to create automated scripts for each manual functional test &#8211; both positive and negative. Remember to create the relevant test data and ensure the data can be reset or refreshed for future automated test execution runs.&nbsp;</p>



<div class="cta-banner-v2">
<div class="title-with-description ">
<p class="title">Automate your mobile tests 10x faster</p>
</div>
<a href="https://testsigma.com/automated-mobile-app-testing" target="_blank" class="cta-btn-v1" rel="noopener">Check out Testsigma</a>
</div>



<h2 id="summary"><span id="Summary"><strong>Summary</strong></span></h2>



<p>Phone number test cases at first seem quite easy and simple. However, once you start testing for all supported formats, there is a great deal of testing to cover. Due to mobile phone number test cases being repetitive, consider using Testsigma to create automated test scripts.&nbsp;</p>



<p>The first step for either automated or manual testing is understanding the relevant requirements and creating a thorough set of test data.&nbsp;</p>



<p>Testers don’t have the luxury of time to continually look up valid phone numbers for every location or country/region. Save your testing time by creating a full set of valid numbers or generating them using a test automation tool. Ensure you have fully covered testing in the field using both positive, negative, and error messaging test cases.&nbsp;</p>



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



<h3 id="what-are-the-negative-test-cases-for-the-phone-number-field"><span id="What_are_the_negative_test_cases_for_the_phone_number_field"><strong>What are the negative test cases for the phone number field?</strong></span></h3>



<p>Test cases for mobile numbers are considered negative whenever the format or character type is invalid. A negative test can also be a violation of the character length.</p>


How to write Test cases for mobile number

Accelq vs Selenium – Which One You Should Choose?

Scriptless Test Automation | What , Why it Matters & Examples


<p>Desk checking is an essential technique in software development and testing that involves a thorough manual review of source code. It is one of the first lines of defense against bugs and errors, providing a unique opportunity for developers and testers to understand and verify code before it proceeds to more formal testing phases. This technique not only aids in detecting errors but also enhances the overall quality and reliability of the software product.</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_Desk_Checking_in_software_testing"><span class="toc_number toc_depth_1">1</span> What is Desk Checking in software testing?</a></li><li><a href="#Advantages_of_Desk_Checking"><span class="toc_number toc_depth_1">2</span> Advantages of Desk Checking</a></li><li><a href="#Best_Practices_in_Desk_Checking"><span class="toc_number toc_depth_1">3</span> Best Practices in Desk Checking</a></li><li><a href="#Use_Case_Desk_Checking_for_an_E-commerce_Application"><span class="toc_number toc_depth_1">4</span> Use Case: Desk Checking for an E-commerce Application</a></li><li><a href="#Conclusion"><span class="toc_number toc_depth_1">5</span> Conclusion</a></li></ul></div>
<h2 id="h-what-is-desk-checking-in-software-testing"><span id="What_is_Desk_Checking_in_software_testing"><strong>What is Desk Checking in software testing?</strong></span></h2>



<p>In the realm of <a href="https://testsigma.com/guides/software-testing/" target="_blank" rel="noreferrer noopener">software testing</a>, desk checking is considered a static testing method where code is analyzed manually without executing it. The process involves a developer or a tester going through the code line by line to check for logical errors, syntax inconsistencies, and compliance with coding standards and requirements. This method can be conducted by the coder who wrote the software, a peer, or a testing professional, often involving discussions or sessions where the logic and approach of the code are debated and scrutinized.</p>



<h2 id="advantages-of-desk-checking"><span id="Advantages_of_Desk_Checking"><strong>Advantages of Desk Checking</strong></span></h2>



<p>Desk checking offers multiple advantages that make it an invaluable tool in the software development lifecycle:</p>



<ol><li><strong>Early Error Detection</strong>: By identifying errors at an early stage, desk checking helps in mitigating the costs associated with later stages of testing and maintenance.</li><li><strong>Improved Code Quality</strong>: As errors are detected and fixed early, the overall quality of the code improves, leading to more stable and reliable software.</li><li><strong>Enhanced Understanding</strong>: This technique provides testers and developers with a deeper understanding of the code&#8217;s functionality and logic, which is crucial for effective testing and maintenance.</li><li><strong>Cost</strong>&#8211;<strong>Effective</strong>: It is a cost-effective method of testing as it does not require any additional tools or software and can significantly reduce the future costs of debugging and development.</li><li><strong>Facilitates</strong> <strong>Collaboration</strong>: Desk checking often involves multiple members of the development team, fostering better communication and collaboration, and shared understanding of the project goals and methodologies.</li></ol>



<h2 id="best-practices-in-desk-checking"><span id="Best_Practices_in_Desk_Checking"><strong>Best Practices in Desk Checking</strong></span></h2>



<p>To maximize the effectiveness of desk checking, consider the following best practices:</p>



<ol><li><strong>Include Diverse Team Members</strong>: Engage individuals from different backgrounds such as development, testing, and design to provide multiple perspectives.</li><li><strong>Prepare and Plan</strong>: Ensure that the code is well-documented and that all necessary materials (such as requirements, design documents, and coding standards) are available before the session.</li><li><strong>Use Checklists</strong>: Develop checklists based on common error patterns in previous projects to ensure that critical aspects are not overlooked.</li><li><strong>Record Findings</strong>: Document all observations and decisions made during the desk check for future reference and action.</li><li><strong>Follow Up</strong>: It’s essential to address the findings from desk checking promptly. Plan follow-up sessions if needed to verify that corrections are properly implemented.</li></ol>



<p><strong>While conducting desk checks, there are certain pitfalls that need to be avoided:</strong></p>



<ol><li><strong>Overlooking Complexity</strong>: Complex pieces of code should be given extra attention and might require more time or a different approach to thoroughly understand and check.</li><li><strong>Bias</strong>: There can be a tendency to overlook errors in one&#8217;s own code or to not critique a peer’s code thoroughly. An unbiased approach is critical.</li><li><strong>Inadequate Preparation</strong>: Without proper preparation, desk checking sessions can be less productive. Participants should be well-prepared with a good understanding of the code and related documents.</li><li><strong>Lack of Engagement</strong>: All participants should be actively involved in the process to provide insights and identify potential issues.</li></ol>



<h2 id="use-case-desk-checking-for-an-e-commerce-application"><span id="Use_Case_Desk_Checking_for_an_E-commerce_Application"><strong>Use Case: Desk Checking for an E-commerce Application</strong></span></h2>



<p><strong>Scenario:</strong></p>



<p>An e-commerce company is developing a new feature for their online shopping platform that allows users to apply multiple discount codes at checkout. The development team has just completed the initial coding phase of this feature.</p>



<p><strong>Steps</strong>:</p>



<ul><li><strong>Preparation</strong>: <ul><li>Developer prepares the code and documentation, including the logic flow and any assumptions made during development. </li><li>A meeting is called to conduct the desk check.</li></ul></li><li><strong>Initial Review</strong>:<ul><li>Developer presents the code, explaining the logic they implemented to handle multiple discount codes and how they interact with existing features like promotional discounts and loyalty points.</li><li>QA engineer reviews the code line by line, checking for logical consistency and adherence to the requirements specified in the design document.</li></ul></li><li><strong>Identification of Issues</strong>:<ul><li>QA engineer identifies a section of the code that could lead to a race condition where two discounts are applied simultaneously in a way that exceeds the total cart value.</li><li>BA’s acknowledge the oversight and discuss possible solutions with developers.</li></ul></li><li><strong>Resolution and Action Items:</strong><ul><li>The team agrees on a strategy to modify the code to handle exceptions more gracefully, including adding additional checks for discount combinations that are not allowed.</li><li>Developer takes notes on all feedback and agrees to revise the code accordingly. They schedule a follow-up session for the team to review the changes.</li></ul></li><li><strong>Documentation and Follow-up</strong>:<ul><li>QA engineer documents the findings and the agreed-upon action items in the project&#8217;s issue tracking system.</li><li>Project manager updates the project timeline to include additional time for re-testing the updated feature.</li></ul></li><li><strong>Code Revision and Re-check</strong>:<ul><li>Developer revises the code, incorporating all feedback. Once the updates are made, he invites the team for a second desk check.</li><li>The team reviews the revised code, confirming that all previously identified issues have been resolved effectively.</li></ul></li><li><strong>Final Approval and Move to Testing:</strong><ul><li>QA engineer prepares to conduct <a href="https://testsigma.com/blog/formal-testing/" target="_blank" rel="noreferrer noopener">formal testing</a>, including both automated and manual test cases, to ensure the feature works as expected under various scenarios.</li></ul></li></ul>



<div class="cta-banner-v2">
<div class="title-with-description ">
<p class="title">Stay up to date with such resourceful blogs</p>
<p class="description">Subscribe to our monthly newsletter</p>
</div>
<a href="https://testsigma.com/newsletter/" target="_blank" class="cta-btn-v1" rel="noopener"> Join our QA Community</a>
</div>



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



<p>Desk checking is a fundamental practice in the testing strategy of any software development project. It not only helps in identifying and fixing errors early but also promotes a deeper understanding of the code among team members. By adhering to best practices and being mindful of common pitfalls, teams can effectively leverage desk checking to enhance software quality and reduce development time and costs. As technology evolves, the principles of desk checking remain relevant, underscoring its importance in achieving high-quality software products.</p>
