-
Notifications
You must be signed in to change notification settings - Fork 13
Version control integration not working #19
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 occasio 8000 nally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@gjb1002 please recheck, I only tested git here |
I get a Git menu showing now, but trying to e.g. select "Git log" produces Traceback (most recent call last): |
Same goes for Mercurial and Bazaar: menus come up fine, so the checked in changes are correct, but then I get the above stack trace when trying to do anything from the GUI. |
(There is a question whether version-control integration really adds anything to TextTest these days. I personally prefer to use dedicated GUIs like SourceTree and GitExtensions now, which are far better than they were 10 years ago. At least we should probably drop support for bzr when TextTest itself has moved away from it, and maybe hg too which I also think is losing the battle.) Have now been using TextTest with Git integration broken for a couple of months, and really haven't missed it... |
I did not try any menu items so this one just slipped through and was easy to fix. I like the log view here but beside that I agree with you. |
I now get this stacktrace instead: Traceback (most recent call last): |
Seems to work now. Tested Git, Mercurial and Bazaar logs and most other menu items on Git. |
I will have a short look on that one when I'm back on windows but if it is not used we can also remove it. |
Just comes silently disabled in the GUI. Suspect some exception is being caught and conclusions are being drawn that it should not be used.
The text was updated successfully, but these errors were encountered: