Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 318268 - cannot test invalid status transitions on Bugzilla 3.6.1
Summary: cannot test invalid status transitions on Bugzilla 3.6.1
Status: RESOLVED WORKSFORME
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 minor (vote)
Target Milestone: 3.5   Edit
Assignee: Charley Wang CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 259291 311966
  Show dependency tree
 
Reported: 2010-06-29 00:44 EDT by Charley Wang CLA
Modified: 2011-01-13 23:04 EST (History)
2 users (show)

See Also:

Attachments
Relocate descriptor files (7.38 KB, patch)
2010-06-29 01:04 EDT, Charley Wang CLA 		no flags Details | Diff
mylyn/context/zip (791 bytes, application/octet-stream)
2010-06-29 01:04 EDT, Charley Wang CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Charley Wang CLA 2010-06-29 00:44:41 EDT 
The transition ASSIGNED --> NEW is throwing a CoreException. Putting a try/catch around the submitTask call does not resolve this issue.

It's possible this was caused by a switch to Bugzilla 3.6.1, I am tracking down the issue.
Comment 1 Charley Wang CLA 2010-06-29 01:04:18 EDT 
Created attachment 172984 [details]
Relocate descriptor files

The issue was caused by BugzillaFixture which used the Repository info to find a descriptor file. When the test repo was updated to 3.6.1 the descriptor file was no longer found. The proposed patch moves the descriptor files so that there is no longer a dependency on the Bugzilla version.

I retested with these changes on the 3.6.1 custom workflow repository, and the test runs without errors.
Comment 2 Charley Wang CLA 2010-06-29 01:04:19 EDT 
Created attachment 172985 [details]
mylyn/context/zip
Comment 3 Frank Becker CLA 2010-07-12 16:47:02 EDT 
Charley,

I think we have fixed this with bug#318112.

Please verify!