Full Code of automationhacks/testing-checklists for AI

Repository: automationhacks/testing-checklists
Branch: master
Commit: 3ddf9380ebf4
Files: 4
Total size: 18.8 KB

Directory structure:
gitextract_4kpy4psp/

├── .gitignore
├── LICENSE
├── README.md
└── mobile_testing.md

================================================
FILE CONTENTS
================================================

================================================
FILE: .gitignore
================================================
# Byte-compiled / optimized / DLL files
__pycache__/
*.py[cod]
*$py.class

# C extensions
*.so

# Distribution / packaging
.Python
build/
develop-eggs/
dist/
downloads/
eggs/
.eggs/
lib/
lib64/
parts/
sdist/
var/
wheels/
pip-wheel-metadata/
share/python-wheels/
*.egg-info/
.installed.cfg
*.egg
MANIFEST

# PyInstaller
#  Usually these files are written by a python script from a template
#  before PyInstaller builds the exe, so as to inject date/other infos into it.
*.manifest
*.spec

# Installer logs
pip-log.txt
pip-delete-this-directory.txt

# Unit test / coverage reports
htmlcov/
.tox/
.nox/
.coverage
.coverage.*
.cache
nosetests.xml
coverage.xml
*.cover
*.py,cover
.hypothesis/
.pytest_cache/

# Translations
*.mo
*.pot

# Django stuff:
*.log
local_settings.py
db.sqlite3
db.sqlite3-journal

# Flask stuff:
instance/
.webassets-cache

# Scrapy stuff:
.scrapy

# Sphinx documentation
docs/_build/

# PyBuilder
target/

# Jupyter Notebook
.ipynb_checkpoints

# IPython
profile_default/
ipython_config.py

# pyenv
.python-version

# pipenv
#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
#   However, in case of collaboration, if having platform-specific dependencies or dependencies
#   having no cross-platform support, pipenv may install dependencies that don't work, or not
#   install all needed dependencies.
#Pipfile.lock

# PEP 582; used by e.g. github.com/David-OConnor/pyflow
__pypackages__/

# Celery stuff
celerybeat-schedule
celerybeat.pid

# SageMath parsed files
*.sage.py

# Environments
.env
.venv
env/
venv/
ENV/
env.bak/
venv.bak/

# Spyder project settings
.spyderproject
.spyproject

# Rope project settings
.ropeproject

# mkdocs documentation
/site

# mypy
.mypy_cache/
.dmypy.json
dmypy.json

# Pyre type checker
.pyre/


================================================
FILE: LICENSE
================================================
                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.


================================================
FILE: README.md
================================================
# testing-checklists

> A curation of different checklists for testing and automation

A testers brain requires a lot of creativity and the no of scenarios that we test on a day to day basis are innumerable. Expecting the *brain* to remember all the ways of testing an application whether it be from a mobile, a web or an API interface is tough and an overhead.

These checklists are a brain dump of the different ways that I approach and think about testing apps in different conditions and hopefully reduces the cognitive load to remember these.

Hopefully these can give you inspiration to adapt and add more items for your needs as well.

## Currently available checklists

- [Mobile app testing](/mobile_testing.md)

For more useful tips and tricks on testing, automation and programming. Check out [automation hacks blog](https://automationhacks.blog)

================================================
FILE: mobile_testing.md
================================================
# Mobile app testing checklist

## App gestures

What actions can the user do on the app?

- [ ] Swipes
- [ ] Taps
- [ ] Pinches
- [ ] Type
- [ ] Hold
- [ ] Drag and drops

## Visuals

Do the icons, images look okay and help the user in using the app?

- [ ] Does the apps, icons, images convey the correct info to the user?
- [ ] Images should fit the screen

## Push notifications

Does the app generate and handle push notifications correctly?

- [ ] Correct text for different app states?
- [ ] Tap on PN to redirect user to correct screen

## Interruptions

How does the app respond to any interruptions while use?

- [ ] If put in background and resumed
- [ ] If killed and restarted
- [ ] If Incoming call, message, PN causes the user to switch context

## App permissions

Does the app require correct level of permissions and the behavior around those

- [ ] Behavior when the user grants/revokes certain permissions
- [ ] Only necessary permissions are requested

## User Input

Does the app handle different types of inputs and allows user to enter invalid inputs?

### Boundary values

Check for value/length as per below:

- [ ] min
- [ ] min - 1
- [ ] max
- [ ] max + 1

### Inputs

- [ ] Overflow values (Enter value > max allowed value for a given data type of the field)
- [ ] Null/Empty/Blank
- [ ] Non ASCII characters (Swedish/Russian)
- [ ] Copy paste values
- [ ] Special Chars (!@#$%^&*())
- [ ] Leading or trailing whitespaces
- [ ] Line breaks
- [ ] String characters (If numeric) and numeric (If String)
- [ ] Numeric separators (1000, 1.000, 1,000)

### Date and Times

- [ ] Future datetimes
- [ ] Past datetimes
- [ ] Invalid datetimes (32 days, 13 month, 25 hours, 61 minutes, 61 second)
- [ ] Holidays
- [ ] Weekends
- [ ] Leap days
- [ ] Timezones
- [ ] Different datetime formats

## Onboarding flows

- [ ] UX when a first time user engages with the app (Introduction flows)
- [ ] These flows should be shown only a certain no of times
- [ ] How do we introduce user to new features in the product? Ease of comprehension
- [ ] Check different user personas

## App upgrades

- [ ] Does app work when upgraded to a new version?
- [ ] Can user proceed with any in-flight flows after app upgrades?

## Screen sizes

- [ ] How does the app look when opened in devices with different screen sizes (4, 5, 6 inches)
- [ ] Does it look okay on a tablet?
- [ ] Does it look okay on a Desktop/Laptop screen (If applicable)

## Feature Toggles

How does the app respond to future toggles

- [ ] Feature turned ON
- [ ] Feature turned OFF
- [ ] Any data created with old/new app should be compatible and should not lead to app crashes

## Error conditions

- [ ] Correct error messages are displayed in different conditions
- [ ] CTA (Call to action) should be as per the application flow (e.g. Do not ask user to retry in case of any terminal state in the app)

## Navigations

- [ ] Back button
- [ ] Sortnig on columns (In case of a list/table control)
- [ ] Pagination (Move forward on last or move backward on first)

## Security

- [ ] SQL Injections
- [ ] App should never show sensitive db, server informations
- [ ] App should handle different user roles and ensure correct information is displayed to the user with his role/priviledges
- [ ] Local storage should not show sensitive information

## Performance

How responsive is the app when:

- [ ] When too many apps are open
- [ ] When app is used in low memory configs/devices
- [ ] Normal load
- [ ] X times normal load
- [ ] Extremely high load from concurrent users

## Backend responses and conditions

- [ ] Status codes check
- [ ] 2XX (Success)
- [ ] 3XX (Redirects)
- [ ] 4XX (Client side errors - Bad requests)
- [ ] 5XX (Server side errors)
- [ ] Does the app block the user from proceeding when waiting for an API when not needed?
- [ ] Does the app engage user while waiting for an API response (with an animation/loader)
- [ ] How the app handles when the API times out?
- [ ] How the app handles cases when server is undergoing deployments?

## Usability

How easy and friendly is the UI for use?

- [ ] Text/font are readable in different mobile sizes
- [ ] Font colors should enhance readibility
- [ ] Show numeric numpad when nos have to be entered
- [ ] Correct use of colors should be made on UI controls
- [ ] Spelling and grammar
- [ ] Localization
- [ ] Links should not be broken
- [ ] Scroll bars should be displayed when needed
- [ ] Scroll bars should be hidden when not needed

## Accessibility

Think how the app can be friendly to people with deficiences (Blind, deaf, dumb, vision related issues)

- [ ] App should be accessible via screen readers / voice commands
- [ ] Accessibility ids should be available with valid text
- [ ] Color should not be relied upon as the single way of identifying content (meaningful texts)
- [ ] Clearly shows when an object on the screen is active
- [ ] Links/buttons with same text but different targets should be uniquely identifiable
- [ ] Sufficient instructions for all interactive elements on the page
- [ ] Sound/video should have text alternatives to explain context
- [ ] Contrast of texts, icons, images should be accessible to people with vision deficiences
- [ ] User should get prompted if a flow gets timed out