jean jayet wrote: > The Webstack QA is pleased to announce the completion of build79 > validation campaign > > > Overall summary > =============== > > This report aims at providing an assessment for the Webstack integration > in Nevada build79. The validation campaign has been executed against > Nevada build 79 for the period from Dec 3rd 2007 to Dec 14th 2007. Both > functional and integration testing have been covered. Functional testing > focus has been done for AMP components subset. > With Nevada build79 15 new bugs have been filed (1 P2, 12 P3) vs 6 P3 in > previous Nevada build 78. > Overall test results can be considered as acceptable. Some functional > bugs would require to be fixed in the next builds planned for SXDE 01/08 > RR to ensure feature completness and increase functional quality. > QA is confident these issues will be fixed within the SXDE 01/08 timeframe. > > > Key highlights > ============== > > * With nevada Build 79 the first version of the Developer Tools > WebStack Admin environment ships all expected features but needs to be > enhanced from an usability standpoint. In addition, some functional bugs > have been filed to highlight some robustness problems, along with a RFE > for the php/mysql delivred sample not that much user friendly. The > Webstack Admin being the end user entry point for the webstack, we have > to pay high attention on it. > I agree. The sample will be updated in b79a, and some of the filed issues fixed:) Thanks for the emphasis on usability tests,
Ludo ps: if we have php gurus on the list, I can get some help for the php sample. > * As regards the AMP components non regression functional testing > the results show up : > o the MySQL component confirms it has reached a good > stability with high pass rate (99%), one issue exists on the sparc only > (bug 6643825), the 2 others tests failed are coming from test itself. > o although PHP pass rate decreases with B79 (70 % vs 80 % in > B73) because of a significant list of missing extensions increasing the > number of unresolved tests (715 in B73 vs 1129 in B79), the number of > tests failed is much lower (13 in B79 vs 50 in B73). The number of new > unresolved tests is mainly due to less extensions integrated in B79 > (that were present in B73) > o similarly, for Apache, as webstack integration delivers the > modules most demanded by the community a certain number of missing > extension impacts the pass rate (see bug 6634926 closed by Engineering). > Globally pass rates are better in B79 (especially for httpd-tests moving > from 37% to 71%) > o A couple of issues affecting the level of functionality of > the Webstack in this build79 have to be fixed in the next builds to > ensure feature completness : like for instance ability to add extensions > for Apache not working, Webmin not integrated for all components, man > pages not available for all components > > * Integration testing is successful with : > o setup and deployments of the short list web applications > (refer to > http://jese-qa.france/SAMP/docs/integration_testing_test_plan_0.2.html > section 2.0) > o End-user scenarios executed on these web applications all > passed > > > Detailed report > =============== > > http://jese-qa.france/SAMP/docs/Test_Report_nvb79.html > > test report is also available of the wiki of webstack QA at > https://twiki.france/bin/view/WebStackQA/TestReports > > > rgds, > webstack QA > > > _______________________________________________ > webstack-discuss mailing list > webstack-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/webstack-discuss >
