Hi all,

Mainly decision were on HTML reporter (Web) and some URL pattern, since
other are fine.


   - http://localhost:9763/automobile/test[/{folderName}]*[/{fileName}][/{ID}],

ID was not validate  as we integrate with automation test framework. We
drop above pattern and come with

   - 
http://localhost:9763/automobile/test[/{folderName}]*[/{fileName}][/{fullName
}]

FullName contains 'SpecName' and 'TestSuite Name'.
JSON API will upgrade API where can be passed test Suite rather fullName,
with 'it_'

   -
   
http://localhost:9763/automobile/test[/{folderName}]*[/{fileName}][/it_{testSpecName
}]


*Web UI*

   - All checked box are to be cheeked in first loading
   - Top checked box is used to 'selectAll' and 'deSelectAll' rather buttons
   - Run button to down from banner
   - Summary of test report will be in top (Banner level)
   - In summary report will have total test count, selected count, pass and
   fail counts
   - When test failed error message will be down of the test with labeling
   of 'Failed'
   - Test message will be explaining, What it was expecting but what was
   there as output of the test.



*For 1.1 V*

   - Grouping test Suite with testSpec name label level as windows(1.1V)
   API with parentID(1.0V)Button to New button for to run all failed
   test(depending on time we go for these even)

Here is mock-up user interface design

[image: Inline image 1]


 *Documentation and sample*

   - Documentation wikipage
   - (sample app) / ES store jaggery module sample test


Thanks
-- 
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com

*Mobile*: +94774066336
*Blog*: http://madhukaudantha.blogspot.com/

<<ui2.png>>

_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to