πŸš€ThinkRuddick QA
πŸš€ThinkRuddick QA
    • πŸ“’ Welcome
    • ♻️ SDLC
    • πŸ—£οΈ Communication
    • 🫴 Requirements
    • 🧭 Planning
    • πŸ—’ Templates
    • 🎩 Status
    • πŸƒ Progress
    • πŸ§‘β€πŸ”¬οΈ Tasks
    • βœ… Acceptance Criteria
    • πŸ“¦ Releases
    • πŸ™‚ Emoji Usage
    • πŸ›° Test Reports
    • πŸ’­ QA Principles
    • πŸ§ͺ Methodologies
    • ⏲️ Timelines
    • 🏒 Deployments
    • 🏝️ Environment
    • 🧰 Tools
    • πŸ§ͺ Cypress
    • 🎭 Playwright
    • ⬛ Black Box Testing
    • πŸ—ΊοΈ Exploratory Testing
    • πŸ™ Testing Library
    • πŸ“± Browserstack

⏲️ Timelines

  • QA should be involved in the project as early as possible and test as often as possible. The more context on business requirements, expectations, resources, risks and priorities - the higher the quality. Generally they will test each new individual feature as it is developed before it is deployed to production.
ProcessesπŸ§ͺ Methodologies
Processes🏒 Deployments