Posted by Sid Herbage on 23/08/2012 01:12:16:
Posted by Michael Gilligan on 22/08/2012 21:27:58:
There are many of us that are interested in this problem, so; why not let the developers make a few test postings … we could then report on performance in different browsers.
You can check the validity of a web page with the W3C CSS Validation Service. This particular page shows 12 errors. Other pages here show various numbers of errors. Perhaps it would be better if the developers cleaned up these before resorting to test postings.
Agreed 100%, Sid … they need to clean up the evident defects in the code before [but not intead of] doing any test postings.
The sequence is pretty well established:
1. Development
2. Browser Compatibility Testing
3. Stress Testing and Penetration Testing
4. User Acceptance Testing
… repeat as required.
"In the Real World": The effort put into each stage tends to vary, according to:
(a) the Budget available, and
(b) the perceived Impact of failure.
MichaelG.