What’s the progress on the “more information” w.r.t the test automation picture. I’ve been waiting a few months now for more info on this to allow me to extract the test results and also for a better way to fire off the tests using a Continuous Integration solution.

Currently I have to resort to screen scraping the html page to report on the results! I’ve written a custom logger that I’ve plug into the testing framework, but I still don’t know how to export the results to show it on our build server.

Thanks

This information would be much appreciated.

2. Some sort of documentation would be nice as well. Thorough documentation is perhaps too much to ask for, but an example of how to use the WorkItemTest class would be useful.

Do you have any idea?

Test method DataAccessTest.SPStorageTest.GetSubDirectoriesTest threw exception: System.InvalidOperationException: ConfigFileMissing —> System.Xml.XmlException: Xml_InternalError.

System.Xml.XmlXapResolver.GetEntity(Uri absoluteUri, String role, Type ofObjectToReturn)
System.Xml.XmlReaderSettings.CreateReader(String inputUri, XmlParserContext inputContext)
System.Xml.XmlReader.Create(String inputUri, XmlReaderSettings settings, XmlParserContext inputContext)
System.Xml.XmlReader.Create(String inputUri, XmlReaderSettings settings)
System.ServiceModel.Configuration.ServiceModelSectionGroup.GetSectionGroup()
System.ServiceModel.Configuration.ServiceModelSectionGroup.GetSectionGroup()
System.ServiceModel.Configuration.ServiceModelSectionGroup.get_Current()
System.ServiceModel.Description.ConfigLoader.LookupChannel(String configurationName, String contractName, Boolean wildcard)
System.ServiceModel.Description.ConfigLoader.LoadChannelBehaviors(ServiceEndpoint serviceEndpoint, String configurationName)
System.ServiceModel.ChannelFactory.ApplyConfiguration(String configurationName)
System.ServiceModel.ChannelFactory.InitializeEndpoint(String configurationName, EndpointAddress address)
ctor(String endpointConfigurationName, EndpointAddress remoteAddress)
ctor(String endpointConfigurationName)
CreateSimplexFactory()
CreateChannelFactory()
CreateChannelFactoryRef(EndpointTrait`1 endpointTrait)
InitializeChannelFactoryRef()
ctor()
WebDesktopPrototyping.RefSPFolder.SiteDataSoapClient..ctor() in D:\Project\KT Web Desktop\WebDesktopPrototyping\WebDesktopPrototyping\Service References\RefSPFolder\Reference.cs: line 2625
WebDesktopPrototyping.Data.SPStorage.GetSubDirectories(String directoryUrl) in D:\Project\KT Web Desktop\WebDesktopPrototyping\WebDesktopPrototyping\Data\SPStorage.cs: line 278
DataAccessTest.SPStorageTest.GetSubDirectoriesTest() in D:\Project\KT Web Desktop\WebDesktopPrototyping\DataAccessTest\SPStorageTest.cs: line 84

- Adding a Timeout attribute, then calling TestComplete from the proper event handler you hook up
- Or, using a private bool or int to track the events being called, plus a delayed callback – EnqueueDelay – that checks and asserts that.

It isn’t perfect, but that might get you started in the right direction. If you examine the open source tests from the Silverlight Toolkit, you’ll see that we do some of this validation throughout the tests.

I am wondering if you might have any suggestions on how one might go about building chained async events for testing.

i.e.
- New up an object and get its contents from a datasource
- Modify the previous object
- Save the object
- Ensure that its data saved correctly

I can get the async testing to work for this in separate parts but I’d like to be able to test the sequence of events. I’ve tried making private async methods and this didnt work, I’ve also trying enqueuing tasks on the callback function and these just blow through and aren’t really ‘reached’ in the traditional fashion. If you need more information let me know. Thanks.

Only problem I am having that when I was testing code that spawned a background worker that lead to some asserts that while they fired, errors in the background thread and the asserts have no effect on the overall unit test (a failed assertion resulted in a passed test).

Now my guess is that the UI thread has to do the assertions, however I am dealing with a Silverlight DLL atm and not a full blown app so I don’t have an easy way to get a dispatcher.

Now I don’t want to say “Gimme Dispatcher” but this overall issue is something to possibly look into. The Visual Studio Debugger stops on failed assertions so I have a workaround for now.

Request for article:
How to get this unit test framework to play with continuous integration as well as calculating test coverage? (i.e. by running in TFS or TeamCity, and speaking with nCover or such

Reactive is a prototype assembly that allows some of the Silverlight Toolkit tests to have a more fluent nature to them.