Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Serenity/JS could show where the changes between releases have been made in SCM tool (git) and highlight areas that have not been retested #3441

Open
1 of 3 tasks
jfstephe opened this issue Apr 16, 2024 · 0 comments

Comments

@jfstephe
Copy link
Contributor

What's the Problem You're Trying to Solve?

Manual (bear with me) regression test suites can become large and slow to execute. Ideally we'd only regression test the areas of the code that have been affected by modifications since the last release.

I don't think any tool out there ATM has this capability as most test case management tools are so far removed from the code bases they test.

How would you like to solve it?

Are there any alternatives?

Proposed Solution

Using @wakaleo's approach from here for integrating manual testing with feature files through serenity, it's possible to know when a feature was last tested.

Using that information, combined with the information from SCM tools like git it would be possible to create a heat map view (like this) that could be added to Serenity BDD Reporter.

This could be used to guide people as to which areas of the application are more important to focus on for their testing activities.

Alternative Solutions

This is an enhancement.

If you think this is valuable, I'd love to discuss this further.

I think there's possible future enhancements to this to possibly use static code analysis to further improve the heatmap to include dependency information e.g. if you change common function X and that is used in component A, B and D then you should consider regression testing them.

@jan-molak mentioned this may have been something that used to exist?

Implementation Support

  • Contribute the feature myself (with guidance from the Serenity BDD team)
  • Hire the Serenity BDD team for implementation
  • Add it to the Serenity BDD backlog and wait for community contribution
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant