Skip to main content

Keeping test cases in sync with your local repository

Know how to keep the Gherkin-styled scenarios in sync with test cases in TestCollab

Updated yesterday

Targeted readers:

For development teams that maintain their BDD feature specifications (scenarios) in plain text using a shared repository and want them to be synchronized with test cases in TestCollab.

Here are some practical challenges a team may face:

  • Domain experts know the process in and out, but lack technical skills

  • Members lack collaboration

  • Automated and regressive testing is a challenge

  • Managers find it difficult to monitor (automated or manual) test executions

  • Deliveries are delayed or product quality is compromised due to all or some of the above reasons

Integration of BDD practices and TestCollab, which brings modern-day test case management and execution techniques, can help overcome these challanges.

πŸ€” Why?

Let us discuss the benefits to know β€˜why’ this is important.

Macro Level Benefits:

  • Clarity - What is to be done, how it will be done, and the expected outcome are all well documented

  • Collaboration - Stakeholders like clients, domain experts, developers, and testers can ensure that the end product meets both the business requirements and user expectations

  • Better Coverage - Easy tracking of missing or duplicate scenarios

  • Better Code - Clear definition of features and their specifications makes developers' job easier

  • Better Testing - Testers know the scenarios, steps needed to perform an operation and their expected outcomes

  • Better Product - From system analysis to the product design, coding and testing; best quality is ensured

Operational Benefits:

  • Real Time Synchronization - With CI/CD pipelines, it is ensured that the test cases are updated as soon as there is any change in feature specifications and scenarios

  • AI-Powered Test Case Automation Training and Execution - QA Copilot uses simple instructions (as in scenarios) to train itself. No coding knowledge is required for the automation

  • Regression - Every change in the application requires regression testing to ensure feature's integrity. With QA Copilot, this simply requires creating a new RUN

  • Manual Testing Support - Easy test planning, assignment management, execution result logging, and regression support for manual testing

  • Better Monitoring - Dashboards that reflect testing efforts in real time make the life of a manager a lot easier

  • Better Efficiency - Whether automated or not, with TestCollab the testing practices become more efficient and targeted towards the end goal - Quality Product Delivered on Time

πŸ› οΈ How?

Since we have now discussed 'why' we need synchronization, let us see 'how' this works:

Pre-requisites:

  • A repository having features and scenarios in Gherkin format

  • A TestCollab user account with atleast one API token generated

  • testcollab-cli package

  • Id of the TestCollab project where the test cases will be synced
    ​

πŸ“ The command

You only need one command to synchronize your entire repository with test cases in a TestCollab project.

tc sync --project {{your_project_id}}

Test cases populated in TestCollab

✨ Tip: The same command can be used to synchronize test cases after the changes in scenarios or features, have been committed.

More details on the process with an example are available at https://help.testcollab.com/en/articles/12101178-setting-up-a-bdd-project-with-test-collab


​

πŸ“– Related articles

Did this answer your question?