The way we work

1. Agreement about testing goals and process

First task is to agree about testing goals – what needs to be checked and why. This comes out from our conversation, taking in count your wishes and goals. For example, if website doesn’t have very good results in search engines, than you need SEO audit. If your website has visual errors, than you need visual audit, etc.

Second task is to come to agreement about testing process – how and where are registered errors, who will be responsible for retesting after errors will be fixed, etc.

2. Offer, agreement and contract

Knowing your testing goals, we conduct your website’s research and evaluate amount of work, while preparing an offer.

After we agree on an offer, we sign mutual task delivery contract. Sometimes contract is not important, but when we are testing administration site of the website and we will need access information, it is important to discuss confidentiality and safety issues and requirements, that is why a contract is important for both sides.

3. Testing and error registration

While conduction testing of the discussed testing fields, we register all found errors in the system that is accessible to all parties involved in a project.

For error registration we use different tools, depending on the type of each project and client’s wishes (for example: Bugzilla, 16bugs, Google Excel, etc.).

Errors are registered with the relevant information, like – place where and in what situation error occurred, how it occurred, description of an error, what has to happen after error will be fixed, picture of an error, type (obligatory / recommended task), status.

At the end of the testing you will receive summary about found errors and their amount.

4. Retesting

If our contract anticipates that we conduct retesting after website developer eliminates all discovered errors, we check each error once again, provide explanations, if developer has questions, we approve fixed errors and renew not done, or partially done tasks.

Sometimes retesting needs to be done many times, if the job was done perfunctory, or while fixing one error other occurred (which sometimes happens, if the system doesn’t have thought through technical architecture).

In website testing and audit we use different tools, which are available to anyone for free. You can get acquainted with the testing tool overview on our blog – website testing tools.