đź“‹
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. Test Strategy
  2. Vision of Quality

Creating TestCase

Ministry of Testing

Case Study:

Hi, I just wanna ask how you managed your time in creating test cases and testing at the same time if you only have 2 weeks in every sprint? Sometimes I don’t have time to finish my test case and start testing without a step by step test case, I only have the expected results in every user stories. TIA! btw, I do manual testing in agile development.

sometimes when I’m done creating my test case and devs raise something some of the requirements were changed and I need to update my test case again then suddenly devs are already done developing.

-- Anonymous

Recommendation 1:

1.Once sprint started you have time to write test cases until the task ready for the tests. Based on scenarios you can prepare 50% of your tests.

2. prioritize you work allocate every day some time to prepare test case

3. Mention in retro about your difficulties.

-- Pramod Mandapati

Recommendation 2:

I try to write TCs or document strategy before the Refinement, and update them as the story & discussion progresses. I do a final review / update the week or sprint before the scheduled sprint.

-- Bhavani Krithivasan

Recommendation 3:

In my company, we found we had to balance the number of testers on each sprint team with the number of developers so the testers have time to not only write / update test cases but also write automation. If there's not enough time to write your test cases as well as do testing, you may need another tester on the team.

I tend to write basic test cases as I test, documenting what I do as I go, and if a test case isn't already written my notes are the draft for that case. It saves time. For comparison, my team has three developers (1 is senior) and 2 QA. When my team only had one QA (me) I was tearing my hair out. I made the case with management over and over until they gave our team a second QA. Now testing keeps up with development.

It depends on the velocity the developers and QA can keep up. In my company 3 devs and 2 qa tends to work out well. 4 devs and 2 qa can work well if the devs are cross functional and can help out with automated test writing.

-- Tracey Clark

Reference:

PreviousTest ManagementNextHow to write good TestCase?

Last updated 4 years ago

Was this helpful?

Test Cases Are Not TestingSatisfice, Inc.
This may be my all-time favourite error messageDevelopsense Blog
Logo
Logo
“Manual” and “Automated” TestingDevelopsense Blog
The End of Manual TestingDevelopsense Blog
Testing Problems Are Test ResultsDevelopsense Blog
Logo
Logo
Logo