📋
QASpace-CaseStudies
  • Home
  • Test Strategy
    • Vision of Quality
      • Good Test Coverage
      • ISO 29119 Certification
      • Date Internationalization Format
      • Localization Testing
      • Test Management
      • Creating TestCase
  • How to Test
    • How to write good TestCase?
      • Tips on Testing
      • Pair Testing
      • UserStory to TestCases
      • Optimising the development flow in a Scrum team
      • Rate/Prioritise bug tickets
  • Exploratory Testing
    • Exploratory Testing
      • Creating Test Charters
      • Test Charters
      • Velocity was too high
  • Agile
    • Implementing Scrumban
      • Breakdown Task
      • Common work across teams
      • Sustainable QA process in the organization
  • Philosophy of Testing
    • Brainstorming
  • Metrics
    • Risk Analysis
      • Testing Outsource
      • How to measure Quality?
  • Automation
    • AI-Automation
      • Software through the lens of AI
      • SAP/Salesforce Automation
      • Mobile Automation
      • Solve by automating the GUI?
      • Improve Skill-sets
      • Coding Skills
      • Working in BDD
      • Value of Test Automation
      • UI/API automation asset
      • TDD VS BDD
      • Selenium vs Cypress
      • An important consideration of Test Automation journey
      • Balance Test Automation Development
      • Automation is no longer providing value
      • Define AI in test automation
      • Unique Locators
      • Best Practices as QA, QA Lead, and Automation Engineer
      • Making friends with Imposters
  • Survey/Polls
    • Is QA really a Gatekeeper?
  • Performance
    • Performance Testing
      • Client-Side Performace
Powered by GitBook
On this page

Was this helpful?

  1. Exploratory Testing
  2. Exploratory Testing

Test Charters

Ministry of Testing

Case Study:

Where do you keep your Charters? Just joined a new project and thinking whether to use:

  • Confluence? (may become easily outdated / hard to maintain?)

  • Jira, storing them per epics? (maybe difficult to gather them?)

  • Other suggestions?

Recommendation 1:

I keep all testing documents (including the charts) on Confluence. For me, it’s easy to maintain and anyone can easily find it. I add the link into the ticket because the ticket itself in my context expires really fast and it’s more difficult for me to find and update the ticket comparing to a Confluence page.

-- Ekias Nogueria

Recommendation 2:

I only used TFS/Dev-ops. I created a task/charter template and then made it the child task of whatever Backlog I was testing. That way people could see what I was doing and and I could use it to talk through with the dev's what I had done.

-- Brian Mcroberts

Recommendation 3:

I created charter and session templates in Confluence. It allows me to keep the charters connected to product docs and maintains a history of the sessions that were run.

-- Shawn Conlin

PreviousCreating Test ChartersNextVelocity was too high

Last updated 4 years ago

Was this helpful?