Functional and Non-Functional Testing Checklist

Mod users demand website and applications that are tight, visceral, and feature-rich. For testers, this translates into a wide scope of work, where missing even a small detail can touch product caliber. To streamline the process, this article provides two structured checklist; functional and non-functional that outline the essential country every tester should validate before freeing.

Consider this a guide to check no critical feature or quality panorama is overlooked.

Functional Testing Checklist

If you are new to functional testing, look at the first then move on with this checklist.

• Identify the scope, goals, and purpose of testing.
• Get a clear sight of expected test results & # 8211; how should the software ideally bear in each scenario?
• Analyze the requirements to create test scenarios and corresponding exam cases.
• Recheck your test cases. Ensure that they hold been shaped to provide.
• Ideally, your tests should largely be automated. are too important, but derogate them to only what is most necessary.
• Run exam on a suited testing tool. Tests must execute on legion existent browser-device-OS combinations. That is the lone way to monitor their performance in.
• Once test solution present up, gather test data and liken it to the expected result listed in this checklist & # 8217; s second step.
• Identify if there are any differences between the expected test results and the actual examination result. If so, zero in on the particular test and comb through the specifics of app performance within that test.
• If tests fail, pinpoint the exact step where they failed (your testing tool should have features to enable this). If necessary, resume what locomote wrong and send study across team members/teams.
• Accumulate feedback from the right stakeholder and rerun tests in a similar surround as the first time.
• Repeat the process listed above.

Now, let ’ s quickly double-click on the key points mentioned in the package functional testing checklist:

1. Requirement Analysis For Creating Test Scenarios

The initiatory step to ensuring extensive and actionable test upshot is to make the right test scenario. Test Scenarios must cover every functionality offered by a website or app, as well as all potential user scenarios. This may not always be possible, but it & # 8217; s crucial to cast as wide a net as possible.

2. Run Tests on a Suited Testing Tool

This point acquire that you already receive the right tool to run comprehensive and wide-ranging tests on background and mobile devices, browser, browser versions, and function systems. However, selecting such a tool can be moderately thought-provoking, peculiarly if you are starting out with. To assist the decision-making process, we ’ ve put together a few resourcefulness for you.

3. Pinpoint the Exact Step Where Tests Failed

Obviously, testers can not comb through every line of a trial playscript to calculate out the positioning of an anomaly or error. Whatever tool you choose should help you quickly and effortlessly identify the cause of test failure. For example, when a exam fails, the tools should automatically log a record of the measure where it fails, direct a snapshot of the test in activeness (at that point), record a picture of the same, and basically tag all aspects of the point where the test deviates from optimal doings.

BrowserStacksupply a wide ambit of (both website & amp; app quiz) – Screenshots, Video Recording, Video-Log Sync, Text Logs, Network Logs, Selenium Logs, Console Logs, Appium Logs, Device Logs, and App Profiling for convenient data seizure and reporting.

Functional Test User Flow

Here ’ s an example of how to approach functional examination of a individual web page. When running the functional exam, the next questions, at the very least should be answered:

1. Testing The Sign-Up/Login Forms

• Can the user create a new account in the expected fast steps?
• Can the user register and enter their item securely?
• If the user is blocked for some intellect, does the website cater a link to facilitate them be unblocked? (unless they are stymy for legal intellect)
• Can the user log in with the name and password they have entered while subscribe up?
• What happens when the exploiter enters incorrect credentials?
• How does each login field validate the requirements of the user name and password & # 8211; numeric characters, alphabetic characters, special lineament, etc.)?
• Does the accurate information and linkup show up in the Terms of Use (which users must jibe to before creating an history)?
  

2. Search Field on the Page

Pro tip: Tools like SUSA can handle this autonomously — upload your app and get results without writing a single test script.

• What happens when exploiter inscribe a search condition in the hunt field?
• If the search term is wrong, what is the message show?
• What is the message shown if the search term is not connect to the webpage/website message?
• Is the search field empty by default? Does it display some message such as“ What are you looking for…? & # 8221;
• Does the search field accept alphameric value or special characters?

3. Fields

• Does every battlefield have the accurate prerequisites for entry values?
• If not, assure that when incorrect values are entered in a field, it cast up the appropriate error content. For example:
  • Field with numeric value: Does not accept missive. May accept special fiber count on app essential.
  • Field with alphanumeric values: Accept both missive and number. May accept special fiber bet on app requirement.

If incorrect values are entered, is the appropriate error message displayed? For example, if a user enroll a missive into a battlefield accepting only numeric values, does it throw a message saying“ Please enter only numbers. ”or something similar?

• Does the entered textbook halt within the borders of the lookup battleground?

4. Filters

• How are product, categories, and data points sorted when the exploiter employ the filter function?
• Does every filter work correctly? Some examples of filter would be & # 8211; form lowest to high price (and vice-versa), mode most popular to least (and vice-versa), sort by brand/product name, sort by product type, some form within a specific price range (that the exploiter can enter), sort by color, etc.

5. Pop-Ups

• Do all pop-ups evidence up in response to the correct user action? For illustration, does the right pop-up display itself when the user leave a particular page?
• Is the messaging on each pop-up correct, well-written and straightforward?
• Are buttons/entry fields on pop-ups working as expected?

Non Functional Testing Checklist

Non-functional testing checks the unity of non-functional aspects of the package & # 8211; execution, serviceableness, reliability, security, etc. Broadly, non-functional testing covers all panorama not covered in functional examination & # 8211; constituent not pertain directly to the package ’ s part.

Within non-functional testing, there are multiple subsets like:

• Performance Testing
• Usability Testing
• Reliability Testing
• Documentation Testing
• Compatibility Testing
• Speed Testing

There are multiple other sub-categories of tests within non-functional testing, but the following are the about crucial.

1. Performance Testing

Evaluates how the package work under different weather. Here, the term performance embrace multiple variables & # 8211; speed, constancy, reactivity, and scalability. Testers must put the software through varying levels of traffic, load, and stress conditions to supervise how the software handles difficult circumstances.

2. Usability Testing

Puts a website or app through the most common scenarios users will face when call for the 1st time. Essentially, it verify the character of user experience provided by the coating under test.

Here are a few resourcefulness to help you get started with usability examination.

3. Reliability Testing

Verifies how reliable software is in different surround. For model, how does the app employment in 2G internet conditions instead of 4G connections? Does user progression on the app arrest consistent when a vociferation comes in? If network weather switch from good to bad, does the app sacrifice sure features to remain functional?

Reliability screen designate to find patterns of iterate failures, track the act of loss occurring in a specific length, discover movement of failures, and make the app stable for as many different real-world scenarios as possible.

4. Documentation Testing

Documentation refers to written and visual material that describes, specifies, defines, and manoeuver users in their operation of a ware. Well-written, open documentation that answers most user questions is integral to the success of a product. Without the physician, most exploiter will have a fairly difficult time even getting started with your software, irrespective of how effective and solution-oriented it might be. Before move alive, ensure that your product corroboration is as robust as the merchandise itself.

5. Compatibility Testing

Examines if the software is compatible with different hardware and software constellation & # 8211; browsers, browser versions, operations system, and their multiple edition, third-party integrations, etc.

requires accession to real browsers, devices, and work systems to run test that thoroughly check app behavior in diverse environments. If you do not have access to an in-house twist lab that is consistently updated and flawlessly hold, consider using a like the one render by BrowserStack.

With 3000+ existent browsers and devicesat your fingertips, you can verify website or app functionality when accessed through different browser-device-OS combination. Run manual and machine-driven tests on both the latest and senior hardware/software variations without having to purchase any devices or install any model.

6. Speed Testing

Needless to say, a site should be optimise for the fastest loading times possible. Speed testing is essential to ensure that you are furnish the optimum user experience. And once again, you can easily test your website speed on real browser and devices via BrowserStack ’ s free fastness testing tool & # 8211;.

To identify precisely how fast page loads across respective browsers and devices, enter the URL on SpeedLab. The tool will run through and supervise website swiftness across a range of democratic browser-device combinations.

Ending Notes

Both functional and non-functional tryout must be accomplish with equal meticulous tending. This secure that you release a high-function website or app that pleases customers and users across different locations, access points, and industry requirements. Use the package testing checklists above to regulate a testing strategy that unite efficacy with, and you will have the foot for solid package quality.

Related Guides