You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
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
The text was updated successfully, but these errors were encountered: