Testing the correct functioning of an application is a major issue in software development. Errors happen and cannot (always) be prevented upfront. There are however some approaches to filter bugs already during development
- Unit testing (at the method level)
- Integration testing (at module level: testing "unit-tested" modules)
- System testing (at system level: GUI, usability, performance, security, stress testing...)
- Acceptance testing (testing by the customer (preferably not a developer); popular in Agile software development s.a. XP)
I don't want to go into detail on all of these. Just
google for it to find more infos. The reason for writing this post is that the Google test engineering team has started a series of posts on
their testing blog where they plan to describe Ajax testing in depth. Some of you may be interested so check the link:
Questions? Thoughts? Hit me up
on Twitter
