When people think about website testing, they generally resort to program execution to detect the presence of defects. This type of test, which runs a code snippet that can be a program or a smaller component, is more formally called dynamic testing. Dynamic tests can be performed manually or automatically (using an automated test tool), but always characterized by code execution.
A complement to the dynamic website tests is the static website test. Static tests refer to the passage of the code, the verifications and any website revision that does not require the actual execution of the code itself. Some web links identify this type of tests as “verifications and routes”, leaving the general term “website tests” for any activity that involves code execution.
Although, in essence, it is a semantic issue, it is useful to divide all test activities into two broad categories, since these actions (dynamic and static) form a comprehensive quality control strategy for the entire website project.
Extensive website quality control
To provide extensive website quality control over a typical website development life cycle (SDLC), all project work items must undergo static testing. This means that business requirements, technical specifications and even test plans are subject to static tests (i.e. checks or passes).
Submission of all the basic work elements of a project to static tests implies that the term “software” (in the broadest term static website test) refers to all the work elements of a project. Although this definition (for static testing) is broader than the scope of the term “software” in dynamic website testing, this area implies that all quality control of a website project can be carried out by static or dynamic testing.
Just as dynamic tests can be automated, there are certain static tests that can also be automated. An example of an automatic static website testing tool can be a tool that measures the complexity of the code in a given program. To measure the complexity of the code, it is not necessary to run the program (test), but the measurement can be performed using a website tool. In addition, the structure, the paragraphs used, etc. Commercial requirements or specifications can be verified using an analysis tool so that compliance can be verified (i.e. tested).
In general, static tests of work items (such as business requirements) involve a standard or format that can be used as a reference. Many companies have procedures that facilitate the 먹튀 verification that a particular work item is compatible. This type of static test (i.e. standard verification) will be documented and planned as part of the project website quality control plan.
Given the categorization of all website tests in static or dynamic groupings, a comprehensive website quality control plan can be developed at the beginning of the project, which can be referenced to monitor and manage website delivery throughout the SDLC (starting with the commercial requirements).