Sparx Systems Forum

Enterprise Architect => Bugs and Issues => Topic started by: PeterHeintz on April 07, 2017, 06:57:06 pm

Title: Testing features seem to be broken in V13
Post by: PeterHeintz on April 07, 2017, 06:57:06 pm
When you enter a new test you can neither select Run By nor Checked By nor Last Run.
When you try to change Status and Save the error message “Test not run yet. Set the Result to the default i.e. ‘Not Run’ is shown !?!?!?

Found in build 1310.
Title: Re: Testing features seem to be broken in V13
Post by: VKN on April 10, 2017, 10:27:30 am
When you enter a new test you can neither select Run By nor Checked By nor Last Run.
You need to select the check box against Last Run.
When you try to change Status and Save the error message “Test not run yet. Set the Result to the default i.e. ‘Not Run’ is shown !?!?!?
You need to select the check box against Last Run and set Run By before you set the Status.
Title: Re: Testing features seem to be broken in V13
Post by: PeterHeintz on April 10, 2017, 06:30:09 pm
Hi VKN,
I see, in V13 some constraints seem to be introduced. I am still not sure if this new constraints providing a value or not. Anyhow, the text in the message boxes (when doing something wrong) are somehow misleading.
Title: Re: Testing features seem to be broken in V13
Post by: qwerty on April 10, 2017, 07:02:11 pm
Do you want to continue? YES, NO, CANCEL

q.
Title: Re: Testing features seem to be broken in V13
Post by: VKN on April 11, 2017, 09:59:36 am
Hi VKN,
I see, in V13 some constraints seem to be introduced. I am still not sure if this new constraints providing a value or not.
Looks like it is trying to avoid a test case getting into an incorrect state. For instance, coming across a test that is set to Pass/Fail but don't know who ran it or when.
Title: Re: Testing features seem to be broken in V13
Post by: PeterHeintz on April 11, 2017, 07:03:57 pm
Yes it seems so.
But once you have set Last Run, Run By and Status to fail (let’s say 3 years ago) someone can change status to Pass e.g. by mistake to get something incorrect as well.
EA is quiet lax in constraining the users, but here in this special case it is not any more since V13.