Web application development: Difference between revisions

Revision as of 18:45, 9 February 2020

Revision as of 18:45, 9 February 2020

Line 21:

Web application clients vary greatly, hence teams might perform some additional testing, such as:

* Security,

* [[Software performance testing|Performance]], [[Load testing|Load]], and [[Stress testing|Stress]],

* Security

* [[HTML]]/[[Cascading Style Sheets|CSS]] validation,

* [[Software performance testing|Performance]], [[Load testing|Load]], and [[Stress testing|Stress]]

* [[Web accessibility|Accessibility]],

* [[HTML]]/[[Cascading Style Sheets|CSS]] validation

* [[Usability testing|Usability]], and

* [[Web accessibility|Accessibility]]

* [[Cross-browser]].

* [[Usability testing|Usability]]

* [[Cross-browser]]

Many types of tests are [[Test automation|automatable]]. At the [[Component test|component]] level, one of the [[xUnit]] packages can be a helpful tool. Or an organization can create its own unit testing framework. At the GUI level, [[Watir]] or [[iMacros]] are useful.