Home | Sign in | English EN
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WindowsLinuxPHPWEBDEV - Browser code
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac CatalystUniversal Windows 10 App
Stored procedures
1. Testing a site: Elements to be tested
Previous pageTable of contentsNext page
Tests play an essential role in the development of a site. The test is used to check the operating mode and the usability of the site.
The main points to check in a WEBDEV site are as follows:
  • how the site works:
    sequence of pages, execution of code typed, etc.
  • appearance of the site:
    use different browsers (Internet Explorer, Chrome, FireFox, Edge, etc.), use different screen resolutions, resize the browser, etc.
  • Web-specific features:
    print, cookies, browser "Back" key, etc.
  • access to the site by different Internet users:
    management of logins and passwords, management of concurrent accesses to the data files, etc.
  • non-regression of a site during an update:
    validate the modifications performed in a site and check whether the non-modified features are still accessible.
  • a stress test (for a site installed on the server):
    validate the maximum number of Web users who can access the site.
Remark: To find out the coverage of tests run, WEBDEV proposes to use "Code Coverage". Code coverage is used to measure the coverage of tests run on a site. Each line of code run is considered as being "checked".
Caution: The code coverage does not allow you to find out whether tests are successful: it only allows you to find out whether the line of code was run.
The code coverage is used to detect the code lines that have never been run.
Previous pageTable of contentsNext page
Click [Add] to post a comment