|
|
| Re: Final Test Pass for 1.1 [message #97885 is a reply to message #97644] |
Thu, 14 July 2005 20:15   |
 Marco Lopez
Messages: 22
Registered: July 2009 |
Junior Member |
|
|
Peter,
I have finished the JVEWRKB01 test scenario and was able to run through the
entire scenario but noticed I had a couple of errors in the .log file but
for the most part it worked as advertised. The main problem I noticed in
executing the script is that the scenario did not match the Eclipse 3.1 GUI
in a couple of places, but those were pretty obvious.
I have looked through the FAQ and other places in order to determine whether
the test passed or failed. I am inclined to say it passed with minor bugs,
but my question to you is if there is an objective set of criteria to
determine PASS/FAIL. I assume crashes or any behavior which prevents the
test scenario from being executed is a fail.
For example, if I am able to run through the entire scenario and then notice
errors in the log file, is that a fail? or a pass with minor bugs? I will
post the bugs I find on the bug submission page you mentioned.
Thanks,
ML
"Peter Walker" <walkerp@us.ibm.com> wrote in message
news:db3e4g$oli$1@news.eclipse.org...
> The final test pass for VE 1.1 begins today. Please see the test pass site
> for registration and the integration driver to use for testing. Look under
> VE 1.1 final regression test -->
> http://dev.eclipse.org/viewcvs/indextools.cgi/%7Echeckout%7E /vep-home/WebContent/docs/testpass.html
>
> Registration is very simple... just click on the Test registration link
> (http://www.eclipse.org/vep/web/testruns/110/final/), look through the
> list of test cases and look for something you would like to test. The
> links to the various test scripts are next to each "Test it" button.
> Clicking on the links does NOT register you... it's just a reference.
>
> When you find a test case you want to test, click on the "Test it" button
> next to the test case. On the next page, type in your email address and
> select "Test it" again. Don't worry... nothing gets sent to your email...
> this is just a way of identifying you as the tester for this test case. A
> notification is sent to the ve-dev mailing list about your registration.
>
> Please open bugs in bugzilla
> https://bugs.eclipse.org/bugs/enter_bug.cgi?product=VE and mention what
> driver you were using.
>
> When you are complete with the test case, post your results (pass/fail and
> any bugs opened) from this same page and another notification is sent to
> the ve-dev mailing list.
>
>
> All are welcome to participate in the test pass... even if you don't want
> to register. Your feedback and comments are always welcome.
>
> Thanks...
>
> Peter Walker
> VE Development
|
|
|
| Re: Final Test Pass for 1.1 [message #97929 is a reply to message #97885] |
Thu, 14 July 2005 21:20 |
Eclipse User |
|
|
|
Originally posted by: jdstinto.us.ibm.com
We usually use the metrics of 3 minor bugs or 1 major bug will fail the
test case. Major obviously would be something that prevents you from
completing, but it could include other serious issues. Sounds like if
you didn't notice there was anything wrong until you look in the log
they might be minor bugs. It would help if you could narrow them down
to the individual events that caused the messages, but sometimes this is
easier said than done.
Also, if the scenario is very out of date please open up a defect for
that and state what is wrong. That way we can fix it for the next test
pass.
Thanks for helping out!
-Jon
> I have finished the JVEWRKB01 test scenario and was able to run through the
> entire scenario but noticed I had a couple of errors in the .log file but
> for the most part it worked as advertised. The main problem I noticed in
> executing the script is that the scenario did not match the Eclipse 3.1 GUI
> in a couple of places, but those were pretty obvious.
>
> I have looked through the FAQ and other places in order to determine whether
> the test passed or failed. I am inclined to say it passed with minor bugs,
> but my question to you is if there is an objective set of criteria to
> determine PASS/FAIL. I assume crashes or any behavior which prevents the
> test scenario from being executed is a fail.
>
> For example, if I am able to run through the entire scenario and then notice
> errors in the log file, is that a fail? or a pass with minor bugs? I will
> post the bugs I find on the bug submission page you mentioned.
>
> Thanks,
> ML
|
|
|
|
| Re: Final Test Pass for 1.1 [message #98069 is a reply to message #97929] |
Fri, 15 July 2005 14:32 |
Peter Walker
Messages: 124
Registered: July 2009 |
Senior Member |
|
|
> Also, if the scenario is very out of date please open up a defect for
> that and state what is wrong.
I opened bug 104012 to track this:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=104012
Regards...
Peter Walker
Jonathan Stinton wrote:
> We usually use the metrics of 3 minor bugs or 1 major bug will fail the
> test case. Major obviously would be something that prevents you from
> completing, but it could include other serious issues. Sounds like if
> you didn't notice there was anything wrong until you look in the log
> they might be minor bugs. It would help if you could narrow them down
> to the individual events that caused the messages, but sometimes this is
> easier said than done.
>
> Also, if the scenario is very out of date please open up a defect for
> that and state what is wrong. That way we can fix it for the next test
> pass.
>
> Thanks for helping out!
>
> -Jon
>
>> I have finished the JVEWRKB01 test scenario and was able to run
>> through the entire scenario but noticed I had a couple of errors in
>> the .log file but for the most part it worked as advertised. The main
>> problem I noticed in executing the script is that the scenario did not
>> match the Eclipse 3.1 GUI in a couple of places, but those were pretty
>> obvious.
>>
>> I have looked through the FAQ and other places in order to determine
>> whether the test passed or failed. I am inclined to say it passed
>> with minor bugs, but my question to you is if there is an objective
>> set of criteria to determine PASS/FAIL. I assume crashes or any
>> behavior which prevents the test scenario from being executed is a fail.
>>
>> For example, if I am able to run through the entire scenario and then
>> notice errors in the log file, is that a fail? or a pass with minor
>> bugs? I will post the bugs I find on the bug submission page you
>> mentioned.
>>
>> Thanks,
>> ML
|
|
|
|
|
|
| Re: Final Test Pass for 1.1 [message #609070 is a reply to message #97644] |
Thu, 14 July 2005 20:15 |
Marco Lopez
Messages: 22
Registered: July 2009 |
Junior Member |
|
|
Peter,
I have finished the JVEWRKB01 test scenario and was able to run through the
entire scenario but noticed I had a couple of errors in the .log file but
for the most part it worked as advertised. The main problem I noticed in
executing the script is that the scenario did not match the Eclipse 3.1 GUI
in a couple of places, but those were pretty obvious.
I have looked through the FAQ and other places in order to determine whether
the test passed or failed. I am inclined to say it passed with minor bugs,
but my question to you is if there is an objective set of criteria to
determine PASS/FAIL. I assume crashes or any behavior which prevents the
test scenario from being executed is a fail.
For example, if I am able to run through the entire scenario and then notice
errors in the log file, is that a fail? or a pass with minor bugs? I will
post the bugs I find on the bug submission page you mentioned.
Thanks,
ML
"Peter Walker" <walkerp@us.ibm.com> wrote in message
news:db3e4g$oli$1@news.eclipse.org...
> The final test pass for VE 1.1 begins today. Please see the test pass site
> for registration and the integration driver to use for testing. Look under
> VE 1.1 final regression test -->
> http://dev.eclipse.org/viewcvs/indextools.cgi/%7Echeckout%7E /vep-home/WebContent/docs/testpass.html
>
> Registration is very simple... just click on the Test registration link
> (http://www.eclipse.org/vep/web/testruns/110/final/), look through the
> list of test cases and look for something you would like to test. The
> links to the various test scripts are next to each "Test it" button.
> Clicking on the links does NOT register you... it's just a reference.
>
> When you find a test case you want to test, click on the "Test it" button
> next to the test case. On the next page, type in your email address and
> select "Test it" again. Don't worry... nothing gets sent to your email...
> this is just a way of identifying you as the tester for this test case. A
> notification is sent to the ve-dev mailing list about your registration.
>
> Please open bugs in bugzilla
> https://bugs.eclipse.org/bugs/enter_bug.cgi?product=VE and mention what
> driver you were using.
>
> When you are complete with the test case, post your results (pass/fail and
> any bugs opened) from this same page and another notification is sent to
> the ve-dev mailing list.
>
>
> All are welcome to participate in the test pass... even if you don't want
> to register. Your feedback and comments are always welcome.
>
> Thanks...
>
> Peter Walker
> VE Development
|
|
|
|
|
| Re: Final Test Pass for 1.1 [message #609082 is a reply to message #97929] |
Fri, 15 July 2005 14:32 |
Peter Walker
Messages: 124
Registered: July 2009 |
Senior Member |
|
|
> Also, if the scenario is very out of date please open up a defect for
> that and state what is wrong.
I opened bug 104012 to track this:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=104012
Regards...
Peter Walker
Jonathan Stinton wrote:
> We usually use the metrics of 3 minor bugs or 1 major bug will fail the
> test case. Major obviously would be something that prevents you from
> completing, but it could include other serious issues. Sounds like if
> you didn't notice there was anything wrong until you look in the log
> they might be minor bugs. It would help if you could narrow them down
> to the individual events that caused the messages, but sometimes this is
> easier said than done.
>
> Also, if the scenario is very out of date please open up a defect for
> that and state what is wrong. That way we can fix it for the next test
> pass.
>
> Thanks for helping out!
>
> -Jon
>
>> I have finished the JVEWRKB01 test scenario and was able to run
>> through the entire scenario but noticed I had a couple of errors in
>> the .log file but for the most part it worked as advertised. The main
>> problem I noticed in executing the script is that the scenario did not
>> match the Eclipse 3.1 GUI in a couple of places, but those were pretty
>> obvious.
>>
>> I have looked through the FAQ and other places in order to determine
>> whether the test passed or failed. I am inclined to say it passed
>> with minor bugs, but my question to you is if there is an objective
>> set of criteria to determine PASS/FAIL. I assume crashes or any
>> behavior which prevents the test scenario from being executed is a fail.
>>
>> For example, if I am able to run through the entire scenario and then
>> notice errors in the log file, is that a fail? or a pass with minor
>> bugs? I will post the bugs I find on the bug submission page you
>> mentioned.
>>
>> Thanks,
>> ML
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.05034 seconds
] 
Search
Help
Register
Login
Home
