Anyone got any examples of runing MSTest in FB6? I'm using VS2008. Tests work fine in VS2008, but the help in FB6 is non-existent. Have messed around with the options with success. Can't even get it to produce an error. It seems to just screw up the whole script.
If someone has it working and can describe the required settings to me it would be much appreciated.
Hi Andrew,
Sorry about the help topic, we’ll get on to that right away.
Have you set the MSTest version to “Visual Studio 2008” in the action configuration? What other settings are you using?
When you say “screw up the whole script”, what exactly do you mean? Would it be possible for you to please copy and paste the output from the action?
Thanks.
- Angus
Yes, I’m using the VS 2008 option.
I know the description of “screw up the whole script” is vague, but it’s difficult to know what’s happening. When I try to run this action nothing happens. It doesn’t go red OR green. Just stays white. I think can’t run the script at all. It doesn’t seem to be paused as the run option is available - but it doesn’t do anything.
As for the options I’m using, well, apart from the VS2008 choice, I’m using the defaults. I know I need more, but I had been hoping the error messages would guide me the know what to do - but obviously that didn’t work out.
My feeling is that the problem might go away if I configure the action correctly - but I don’t know how - hence the need for an example of it in use. I have a VS2008 solution that contains my main project and the test project. I’d like the tests to run at the start of my script, so the script doesn’t continue if they fail.
Any progress since the last post in April on defining a clear example and expanded reference in help for MSTest.
Thanks,
Kevin
Hi Kevin
Yes, there have been several check in’s on this action since April, adding support for running with the stand along mstest install and publishing test results to TFS when FB is run from there (there may be more, I just looked at a few checkin comments). The help was also updated.
Hello Vincent. Since I am new to the VSoft forum could you expand on the following comment: "there have been several check in's on this action". Where can I observe these check ins? I searched the forum yesterday and only found the comments from April. It would be helpful to observe how others successfully tackle executing standalone unit tests although I am moving away from TFS due to its dependencies on other MS products.
Thanks.
Hi Kevin,
The public information is here:
https://www.finalbuilder.com/version-history.aspx
I’d recommend you download and install the latest build.
cheers,
tate.
Hello Tate,
I already have version 6.1.0.891 installed. I was more interested in Vicent's remarks about seeing the "checkins" -- what was meant by that statement.
Anyway for others looking into MS Test here's my comments.
I got MS Test running standalone after about 8 hours of "run and fix". Installed VS 2008 for Testers to get the MS unit test assemblies loaded correctly which are located at "[install-drive]\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PublicAssemblies". Afterwards what I remember the most was manually adding the expected reference path to the VS solution file for my VS project assemblies since my dev workstation has a different drive path than the unit test server. I use a common folder for all the assemblies so it was only a one-liner but it took a couple of hours to understand the problem. I also had to get the "pdb" bebug files to my common assembly folder for code coverage to work properly. On top of all of that, it was critical to run a debug build prior to the unit test run to sync-up assembly versions otherwise the code coverage result file contains a message about not able to find the expected file version. Constantly reviewing the code coverage results file was helpful in resolving issues.
Hope this helps,
Kevin
I was more interested in Vicent’s remarks about seeing the “checkins” – what was meant by that statement.
In response to your question (any progress since April), Vincent looked through the history of the action in our version control system and noticed that there were several changes to that action since April - which meant there has been work done in this area. Our version control system is obviously not public - but what is released are a summary of changes to various actions in each minor update which can be viewed from the version history page.