Like the title says, I have an online app that I am wanting to validate, but users need to log in first to access them. How do I go about validating this?
Thanks! Joel
+4
A:
With this html validator extension. Or by Ctrl-U, copy-paste into the w3c page.
Tobu
2010-01-12 21:38:30
I disagree, this is totally impossible to apply integration testing to. The view is just as important to test as your app, Why do we use complex testing frameworks like Rspec, Shoulda, and Autotest etc. just to serve the final output as untested html. It reminds me of the "super hi-fi" recording artists that record all their music in analog just to ship a super crappy compressed mp3 to their listeners.
Joseph Silvashy
2010-01-13 18:52:24
Feel free to provide an answer with an automated option if you know one (Selenium maybe?). But tests are just a lower bound; they never prove your app will work. Browsing the app will uncover a lot more corner cases, which this kind of extension easily catches.
Tobu
2010-01-13 20:11:23
I'm not asking about integration testing. I'm asking about getting a page validated in W3C if it is behind password protection. This solution worked great. Thanks!
Joel
2010-01-13 21:50:39
+3
A:
Assuming you mean markup validation, log in yourself, go to the page you want, view source, and use the direct input option.
Daniel Schaffer
2010-01-12 21:38:37
+3
A:
You have to run the service they provide on your server:
http://validator.w3.org/docs/install.html
Thats what we've done, works great.
I think it's best practice to be validating your sites source when it's in development not when its in production... Treat this just like running unit tests. You shouldn't have markup errors go live either.
Joseph Silvashy
2010-01-12 21:38:50
+1. Best option if you are worried about the sensitive date on your page.
Chetan Sastry
2010-01-12 21:41:38
Right, but I think it's just best practice to have the app all buttoned up once it time to deploy to production... think about it this way, you don't want to have to redeploy the whole app to the production server risking downtime, dropped user sessions etc just because you forgot to close a tag or something.
Joseph Silvashy
2010-01-12 21:45:03
Well-I think we can all agree that most websites are ALWAYS in development-even after they are live :-D
Joel
2010-01-12 21:45:40
I mean you have your staging version (often called your development version) and your production version, sometimes called the "live version". I prefer to call them "Development" and "Production" but thats just me.
Joseph Silvashy
2010-01-12 21:51:39
+1
A:
I assume you mean w3 validator service. You can copy paste the html contents into the validator or save the html into a file and upload it. If you have Firefox Web developer extension, it provides a 'validate local HTML' option.
Chetan Sastry
2010-01-12 21:39:43