/qa-fortress

Evolving idea of something I call QA Fortress.

qa-fortress

Idea of Quality Assurance Fortress is to set (potentially) automated, open-source type structure of testing tools covered with up to date documentation.

Here are some links:

  • Initial papers - doc file (Here is a preview of all my note-taking's while working, which are being later on implemented into QA Fortress project with note about each action inside changelog.md file)

  • Types of testing approaches - sheet file

  • Local documentation - directory

  • Mindpmup original file (with links available) - mindmup file

How to "mind-map":

Just double click on node to see more and vice versa to retract. 🔍

Please feel free to contribute! 😊 👉 Contribute guidelines

Mental map nodes explained:

  • 'Helpy stuff' - additional (mostly free) tools and accessories that can help you out in your testing environment (difference between them and "TOOLS" node is that "Helpy stuff" has more subjective usage than objective).

  • 'Local documentation' - extract from official documentation on chosen tool; creating through this approach simple and additional usage files for easier ongoing use of chosen tool.

  • 'Support HQ' - "branches" that go beyond QA fields, but from where the trunk stands. 🌴

Mind map *preview for fully expanded mental map.

TODO

  • Arrange project inside robust test management tool or on presentation website with advanced search, or...
  • Create/ extract 'local' documentation - 🚧 work in progress 🚧
  • Update mind map png file on MindMup
  • Add security, blockchain and testing approach components to mind map

More inside - Kanban project list