Jameleon

How many rows in your CSV file do you have in the first test case? 
 
It looks like two rows failed and only the message for the first row is 
available. Are both rows supposed to fail? I hope to add a link to the 
state of the application for each failure in the future for test cases 
that fail multiple times, once for each row in the CSV file. 
 
Quoting Robin.Spark@...: 
 
> Christian, 
>  
> I think I've found a few bugs here... 
>  
> If I put the Tutorial-ValidLogin Test-case (which fails) above the  
> Tutorial-InvalidLogin Test-case (which passes) in the XML file, the  
> Tutorial-InvalidLogin Test-case doesn't run. When the first test-case  
> fails, the second doesn't get executed - is this supposed to be like 
> this? 
>  
> #: 
> Result: 
> Test Case: 
> Execution Time: 
> Run: 
> Failed: 
> Passed: 
> Message: 
> 1 
> ? 
> Tutorial-ValidLogin 
> 0h 0m 5.141s 
> 2 
> 2 
> 0% 
>  
> 
file:/C:/DATA/javadevelopment/jameleon/tst/xml/tutorial/devTestCases-DataDriven.xml:9:-1: 
>  
> <jmln:jameleon-tutorial-page-validator> 
> junit.framework.ComparisonFailure:  
>  
>  
>  
> assertTitleEquals 
>  expected:<...Welcome> but was:<...Invalid Username and/or Password>    
> 2 
> ? 
> JUnitTest 
> 0h 0m 0.078s 
> 1 
> 0 
> 100% 
>   
> 3 
> ? 
> JUnitTest 
> 0h 0m 0.109s 
> 1 
> 0 
> 100% 
>  
>  
>  
>  
> Also, if some of the logins are valid in the Tutorial-ValidLogin.csv 
> file,  
> (as below), ALL 5 test results are reported as having failed - which is  
> not true. 
>  
> "loginUsername","loginPassword" 
> "validUser2","validPassword2" 
> "validUser3","validPassword2" 
> "validUser5","validPassword2" 
> "invalidUser1","validPassword1" 
> "invalidUser4","validPassword2" 
>  
> Log session start time Tue Nov 04 11:03:53 WST 2003 
>  
>  
> #: 
> Result: 
> Test Case: 
> Execution Time: 
> Run: 
> Failed: 
> Passed: 
> Message: 
> 1 
> ? 
> Tutorial-InvalidLogin 
> 0h 0m 5.500s 
> 5 
> 0 
> 100% 
>   
> 2 
> ? 
> Tutorial-ValidLogin 
> 0h 0m 0.985s 
> 5 
> 5 
> 0% 
>  
> 
file:/C:/DATA/javadevelopment/jameleon/tst/xml/tutorial/devTestCases-DataDriven.xml:20:-1: 
>  
> <jmln:jameleon-tutorial-page-validator> 
> junit.framework.ComparisonFailure:  
>  
>  
>  
> assertTitleEquals 
>  expected:<...Welcome> but was:<...Invalid Username and/or Password>    
> 3 
> ? 
> Navigate To Start Page 
> 0h 0m 0.047s 
> 1 
> 0 
> 100% 
>   
> 4 
> ? 
> JUnitTest 
> 0h 0m 0.062s 
> 1 
> 0 
> 100% 
>   
>  
>  
> regards, 
> Robin 
>

Paul, 
 
Thanks for the feedback! 
 
> I'd also like to say thanks for the great program.  Especialy the new 
> version 1.6 it will save us allot of time. 
Thank you. Any feature recommendations would be gladly accepted. 
 
>  
> There are two bugs.  the first is that if a name of a function point 
used 
> in the XML scripts is spelt incorrectly then it will be silently 
ignored. 
>  Jameleon dosn't complain loud enough about this. 
 
This is actually the nature of the beast. I don't have much control over 
this. You see Jelly is meant to be used with other non-Jelly XML. 
Therefor, Jelly ignores XML it doesn't know about.  
 
I added a debugging feature specifically for this. Try setting the "trace" 
attribute to true in either your test case (for the trace logs for the one 
test case) or in the Environment.properties (for all test cases). This 
prints out information as to which functionalId is being executed and 
which one passed/failed. 
 
> The test is marked as 
> passed in the report but failed on the console. 
> 
I am guessing this is when NO asserts were run. Is this the case? If so, 
then on the next release, I plan to add a "?" to the results instead of an 
"X". This way, manual test cases can be stored in Jameleon as well. The 
ones marked as "manual" through another tag, not yet implemented, will 
only be included in the TestResults.html as manual test cases. So there 
will have to be a Check Mark, an "X", a "?" and some other signal for a 
manual test.  
  
> The second is that if you use certain HTML tags in non Jameleon spacific 
> Javadocs  in your function points then it can break the report.  The 
page 
> for that test will fail and not be generated.  It breaks when you don't 
> have an end tag, so you cannot use tags like <br> at all.  I am using 
<p> 
> and </p> as a work arround. 
 
I need to better document this. I am using XSLT to transform the test case 
docs. XSLT needs a well-formed document and some HTML is not considered 
well-formed XML. However, XHTML resolves this issue and all new browsers 
support XHTML. In other words, try <br/> instead. Is that an acceptable 
solution? 
 
Thanks again for the feedback.  
 
Cheers, 
Christian 
>  
> Regards and Thanks. 
>  
> Paul Bone. 
>  
> --- 
> Paul Bone 
> paulb@... 
> Cybersource 
> Ph: +61 3 9621 2377  Web: http://www.cyber.com.au 
>