Best Practices when generate a Pull Request
When a test case author generates a pull request in Bitbucket for review and approval of the branch containing a TestComplete test case, what are the best practices to keep in mind to enable an efficient review process?
When a reviewer looks into the "Diff" tab in bitBucket for the pull reques generated,
a) the "testcaseName.tcKDTest" file generates the .xml version of the test case which could be challenging for some reviewers to understand the flow of the use case & the test data used.
b) similarly the "testcaseName.tcKDTest.tcVis" file generated is also a .xml file
c) browsing through the .png files is the only thing that is currently providing some clue of the work flow.
Solved! Go to Solution.
We always review inside TestComplete.
[Community Heroes] are not employed by SmartBear Software but
are just volunteers who have some experience with the tools by SmartBear Software
and a desire to help others. Posts made by [Community Heroes]
may differ from the official policies of SmartBear Software and should be treated
as the own private opinion of their authors and under no circumstances as an
official answer from SmartBear Software.
The [Community Hero] signature is used with permission by SmartBear Software.