We have Team Foundation Server as a version control system in place. Telerik QA edition seems to be successfully integrating and checking in/out changesets to the repository. However, we have an external continuous integration system (Hudson) that orchestrates our current builds and unit/interface testing. When sourcing from TFS using our CI service, certain files seem to be missing, namely:
Has anybody been able to successfully integrate with TFS, the QA Edition, and a third party orchestration engine?
If we used another version control system (or a client external from Telerik) we could check all those files in, but then we lose the integration that the QA edition offers. Some basic investigation into how the DLL is created yielded a dark path that I don't really want to walk down - namely that the test runner edition can't be used to compile the DLL. Moving to the developer edition with full MS-Test seems a bit heavy given that we enjoy the usability of the QA edition. A trial run using another version control system was successful in executing the tests and reporting results, so we've at least got something working.
- The project DLL that is compiled from our C# code at runtime
- Any test lists that engineers create
Has anybody been able to successfully integrate with TFS, the QA Edition, and a third party orchestration engine?
If we used another version control system (or a client external from Telerik) we could check all those files in, but then we lose the integration that the QA edition offers. Some basic investigation into how the DLL is created yielded a dark path that I don't really want to walk down - namely that the test runner edition can't be used to compile the DLL. Moving to the developer edition with full MS-Test seems a bit heavy given that we enjoy the usability of the QA edition. A trial run using another version control system was successful in executing the tests and reporting results, so we've at least got something working.
1 Answer, 1 is accepted
0
Hello Michael,
We have recently worked on introducing project compile during test execution as well. This made it in the Q3 SP2 build labeled 2010.3.1421. I'd even recommend the latest internal build (1502) that includes some improvements in this area. Please give it a go and let us know if it works fine for you producing the test project DLL.
Please also use QA and RunTime Editions from the same version to avoid any conflicts. You can find the 1502 RunTime internal build available for download too.
As to the TestLists those should be automatically checked-in when you perform the operation for the project. Does that work for you with the latest builds also?
Greetings,
Konstantin Petkov
the Telerik team
We have recently worked on introducing project compile during test execution as well. This made it in the Q3 SP2 build labeled 2010.3.1421. I'd even recommend the latest internal build (1502) that includes some improvements in this area. Please give it a go and let us know if it works fine for you producing the test project DLL.
Please also use QA and RunTime Editions from the same version to avoid any conflicts. You can find the 1502 RunTime internal build available for download too.
As to the TestLists those should be automatically checked-in when you perform the operation for the project. Does that work for you with the latest builds also?
Greetings,
Konstantin Petkov
the Telerik team
Registration for Q1 2011 What’s New Webinar Week is now open. Mark your calendar for the week starting March 21st and book your seat for a walk through all the exciting stuff we ship with the new release!