| || |
CMS Test Methods
I am very curious as of what approach does open source content management systems take to testing.
Is there a formal testing methodology used such as:
- Test Driven Development
- Traditional (RUP, Watefall)
Do the testers follow specific guides or steps whilst undertaking the testing process?
I know as most CMS are community based, so do the developers simply release each build to the public and hope their peers discover these bugs?
And most importantly is there a standard benchmark for testing CMS Portals?
And what type of automated test tools are used?
Thanks in advance,
Re: CMS Test Methods
Let me say what we tried to do here.
We divided the preparation of test cases into three different entities
- User Requirement
- General tests – (eg: password need to be case sensitive etc….)
- Touch and feel test - (eg: Error messages should be appropriate etc….)
- Technical testing.
The testing team will prepare the test cases by these entities in mind which will be go under the review by the PM. The general tests and touch and feel test will be added after each project according to the interest of the client.