PC SOFT

WINDEVWEBDEV AND WINDEV MOBILE
ONLINE HELP

Home | Sign in | English UK
New WEBDEV 24 feature!
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
1. Running a site test: The elements to test
Previous pageTable of contentsNext page
Running the test of a site is an essential step of its development. 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.
Note: 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 code line 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 code line was run.
The code coverage is used to detect the code lines that have never been run.
Previous pageTable of contentsNext page
Minimum version required
  • Version 24
Comments
Click [Add] to post a comment