I'm having a problem while trying to follow a example of Spec Explorer, while using Visual Studio 2012.
I've been following this link, but I get stuck on the running the Spec Explorer file with a Console Application.
My problem starts at the next sentence:
"Running this part of the program on the exploration result file of the TestSuite machine in the SMB2 project results in output as below:"
I don't know how to do this, but they don't elaborate on it, does anyone of you know how I should do this?
I assume you are using Visual Studio (VS)2012.
Then I guess you tried already the "RequirementReport" example of Spec Explorer.
This should give you the same possibilities and a running example (using VS2010).
I assume you tried this example, but it was not working (due to VS2012).
Then you tried it with this article in your link.
You're interested in just a report of an exploration result. You're not playing with the idea any more of creating your own full blown path coverage strategy. Right?
You created a new console-application-C#-project and copied the program code from the end of the article into it.
You are able to compile. But you forgot to replace "args[0]" with the full qualified path to an .seexpl-file! Right?
A lot of guessing, but I need 4 more points until I can ask questions in a comment ...
Related
I understand that nunit console 3 can write to TestResult.xml after running the tests, where the TestResult.xml is located inside the directory specified by --work parameter.
But from what I can tell, TestResult.xml contains too many (irrelevant) details, that I don't need to fix my unit tests errors. All I need is just the failed or ignored test cases, just like what is displayed in command line prompt when I am running nunit console in it.
How to configure the parameters for nunit console 3 so that it only gives me failed or ignored test cases?
Sorry, I'm a few months late (unfortunately I came across this problem only now). But as far as I searched, the only possibility is to use XSL transformation. There are some applications that can convert the XML report file, but... I tested a few, but unfortunately the output was not that was I need.
Therefore I created a simple NUnit3summary application that can transform the standard XML output file to text file. I was surprised that nobody until now made something like this (or at least did not publish it). It were only two hours of work (first working version) and a few more to finish it to stare ready for publishing.
It is only a simple application that was aimed for my needs. You can use filtration for now only with another application, e.g.:
NUnit3summary.exe TestResult.xml | grep Failed >FailedTests.txt
You can see a practical application here (this is also the project where the application was needed, because of too many errors in unit tests).
I've currently got an issue in our Dynamics CRM test environment, we currently cannot 'uninstall' the managed solution we have imported from our development environment.
The error we are getting when we try to uninstall is: "[entity] doesn't have a valid quick find query defined for it.". The log that they allow you to download with 'more details' essentially says the same thing with an error code of -2147089917.
I can't find any information on google or in the dynamics documentation around what could cause this issue or what it means.
We have done some basic customisation to the quick find query for that entity which appears to be in the solution. We can use the search and it uses the quick find query we have defined so that appears to be correct.
The solution we have is exported from our development environment and then imported as a managed solution to the test environment.
We've tried importing a newer version of the same solution over the top and we still can't delete.
Does anyone have any ideas as to what could cause/solve this issue.
Thanks,
Michael
you have to remove the entities existing in the solution which you want to uninstall from the Quick find Search before deleting the solution.
To do this:
go to Settings > Administration > System Settings
In the tab marked “General” you will see a heading called “Set up Quick Find”
Select the record entities that you would like to remove and click OK
And now you should be able to uninstall your solution.
Hope this help!
Thinks,
Youssef.
I want to know where actually these log files got saved in test manager?
As per my understanding, it's saved under SQL server. But I dont know how to get it from it (may be using SharePoint reporting service). If you look the logs, you ll find the link like mtm://<tfsSeverName>:8080/tfs/defaultcollection/p:trunk/Testing/testrun/open?id=118.
I'm trying to find more info. If i get it, I ll post here.
In the mean time, I have created my customized logs with the test case, so that I can use it to debug somewhat.
I have a process for running automated functional tests which is external to Microsoft Team Foundation Server (TFS) 2010. Test cases are tracked as Test Case work items within TFS, however. After running these tests, how can I publish the results to TFS using the TFS API? Can someone point me to sample code that demonstrates this?
Please note that I expressly want to avoid a solution that requires transformation of my test results into the .trx file format. Searches have turned up dead links, or solutions that rely on this method.
It sounds like the following blogs may almost be what you're after
http://blogs.msdn.com/b/jpricket/archive/2010/02/23/creating-fake-builds-in-tfs-build-2010.aspx
http://msmvps.com/blogs/vstsblog/archive/2011/04/26/creating-fake-builds-in-tfs-build-2010-using-the-command-line.aspx
It doesn't actually have code for adding test results, however it does say this:
"In order to associate test results and the like, you have to create build project nodes with the fake build."
You should be able to create a Microsoft.TeamFoundation.Build.Client.TestSummary with a summary of your test results.
There's a couple of internal classes that look interesting, specifically Microsoft.TeamFoundation.Build.Controls.TestRunDetails, which could potentially be useful if you don't mind using some reflection.
However what I would recommend, is using the API to look at the nodes in a standard TFS build to see how they are built up.
I'm trying to use the VssGet task of the MSBuild Community Tasks, and the error message "File or project not found" is beating me with a stick. I can't figure out what in particular the error message is referring to. Here's the task:
<LocalFilePath Include="C:\Documents and Settings\michaelc\My Documents\Visual Studio 2005\Projects\Astronom\Astronom.sln" />
<VssGet DatabasePath="\\ofmapoly003\Individual\michaelc\VSS\Astronom_VSS\srcsafe.ini"
Path="$/Astronom_VSS"
LocalPath="#(LocalFilePath)"
UserName="build" Password="build"
Recursive="True" />
If I write a Streamreader to read to either the database path or the local path, it succeeds fine. So the path to everything appears to be accessible. Any ideas?
Two thoughts. One, sometimes a type load exception manifests as a FNF - let's hope that's not it. But if the code is actually being honest, you can track the problem using Procmon or Filemon. Start one of those utilities and then run your task again. You should be able to track down a record of a file that couldn't be located.
#famoushamsandwich that's a great response -- I had not previously heard of procmon or filemon. Tried procmon on the problem, but even after sifting through the relevant output (my gosh the machine does a lot more stuff behind the screen than I was aware of) I couldn't find where a file I'm referencing wasn't being found.
Procmon and Filemon are good suggestions - just make sure you filter the results to only show errors. Otherwise the success messages will bury the problem entries. Also, you can filter out processes that are not at fault (either through the filter dialog or by right-clicking the entry and choosing "Exclude Process".)
A couple other thoughts:
In the LocalFilePath, you are specifying a single file as opposed to a folder. The task, on the other hand, specifies to get files recursively. Perhaps you need to remove "\Astronom.sln" from the LocalFilePath?
Is the build task being run under your account or another? It's possible you have a permissions issue
Do you already have a copy of the code pulled down in the same location? Perhaps there is a failure to overwrite an existing file/folder?