A few weeks ago I have posted a couple of links to tools to help with testing web apps inside the browser and now I wanted to share another resource meant to help web developers tests their apps.
The project released by Neil Crosby and introduced as Frontend Test Suite is imo more about about validating the various aspects of the front end layer (HTML, CSS, JS) against the standards and not application testing. Anyways it can become part of your automated continuous test suite.
Below is the slide deck of Neil's Automated Frontend Testing:
While I have been validating from time to time some of my web apps, I must confess that such testing has never been part of any of the test suites. Have you used it in any of your projects?
3 comments:
Why not use Merilo? As I cruised around the presentation I noticed some differences, I'll take a look into his FTS tool. I read Rusty Harold's book on html refactoring and it contains some of Crosby ideas. You can use for quick check small tools like Xenu or DRKSpider. During load testing set up Fiddler2 with different agents and imitating different traffic so you can see TTFB and TTLB, and you can also parse the html (if you save it as ) obtain data and compare with the tool you used for load test (i.e. Pylot report against Fiddler concentrated on same load session). Right now, you can add to Fiddler plugins like neXpert.
I must confess that I haven't heard of any of the tools you are mentioning, so thanks a lot. I'll definitely take a look at those.
Thank you, but I think I'm waaay behind you in dealing with tehnologies. Another tool that is small and smart is Jiffy, and it has a firebug plugin. It was presented at Velocity last year. Other nifty little tools also presented there: AOL PageTest, Steve Souders Hammerhead plugin for Firefox. For a deeper look on how you communicate with the application you can try a packet sniffer. Many recommend WireShark. I recommend Rumint Tool.
I don't have a blog so a wrote the tools here. I'm uilcrw on twitter following you :)
Post a Comment