Community | TeamSolutions
TeamSolutions | Enhanced visibility & communication

Test Case 'Open for Edit' button no-op

This post has 2 Replies | 2 Followers

Top 150 Contributor
Posts 1
dbreggin Posted: Mon, Jul 12 2010 11:27 PM

I have VSTS 2010 64bit Ultimate (includes MS Test Manager) installed, fully functional, and completely integrated with TFS.  I have been able to prove all MS TFS functions, including creating new projects of various templates, and etc.

I then installed TeamLook.

Everything appears to function except the TeamLook > Test Case > 'Open for Edit' button.  Clicking on this button does nothing (whether or not MS Test Manager is running).  I expect it to open the test in Test Mananger, ready for editing.  It does not matter if the test has been edited already or not.

Clicking on the same button within TFS Team Explorer (on the exact work item) spawns an instance of Test Manager (if it is not already running) and opens the test for editing.

I cannot determine if this is an installation issue, or a function issue (buggy or not present).  Please advise...

Thanks, Dan

Top 150 Contributor
Posts 1
ARGUSnet replied on Tue, Sep 14 2010 3:29 PM

I have this Problem. Has anyone a solution?

 

Message: Dieser Ordner kann nicht gelöscht werden. Klicken Sie mit der rechten Maustaste auf den Ordner, und klicken Sie dann auf 'Eigenschaften', um die Berechtigungen für den Ordner zu überprüfen. Wenden Sie sich an den Besitzer des Ordners oder an den Administrator, um Ihre Berechtigungen zu ändern.


Source: Microsoft Outlook


StackTrace:    at Microsoft.Office.Interop.Outlook.MAPIFolder.Delete()
   at TeamLookCommon.TLRootFolder2.Sync(Object settingObject)
   at TeamLookCommon.FolderTree.Sync(TLSettingTree newTree)
   at #=qzOhU$BOBHfev1pLobvHU2OH$fpBPnikzKV0jjebpgFI=.#=qvpDl_nkl7c_Fjv3hFBqoFQ==(MAPIFolder #=qKsCHFNZO8WSvJsjSC243CQ==)
   at TeamLookCommon.TLExplorerWrapper.#=qf3gBgkLO$6Cvb$3zQgkT6nZJ4hs_H6PQjpwYB9kwU0s=()

Top 10 Contributor
Posts 104
Joe Buys replied on Tue, Sep 14 2010 7:03 PM

Hello All,

This has been resolved and we plan on having a release later this week which includes a fix for this issue.  The new release will also have a couple cool new features that have been requested quite a bit!

Expect a build on the web early next week.

Cheers,
~Joe

Page 1 of 1 (3 items) | RSS