13 posts tagged with "validation"

Chrome extension for test registration (stable version)​

We have released stable version of the Chrome extension, for the functional test registration directly from the browser.

Functional testing vs healt check​

We have separated the tests into two categories: Health check and Functional.

• Health check is a simple test to validate the status of a single page test, from different points of view like availability, visual and status of third party services / APIs and static files.
• Functional test is a multi-step test can be adopted to validate also the functional aspects of the ecommerce (navigation, search, registration, checkout, ...), in addition to availability, visual and third party services.

Chrome extension for test registration​

We have released our firt beta for the test registration directly from the browser, through the use of a Chrome extension. Finally, we have added another option for the test creation, a no code option. It is now possible, for each device (Desktop, Mobile and Tablet) register the actions executed in the browser, navigating the target e-commerce.

Testing, content always separeted between devices​

From today, the content representing a test will be always separated according to the target device: Desktop, Mobile and Tablet. This restriction has been introduced in order to make more understandable and usable the editing and mainteinance process of the created tests.

Testing, editing, copy content from other device​

The "Copy content from" has been introduced in order to allow the actions copy from one test content (device) to another one. This feature simplify the creation of the test, immediatly having all the actions, created from another device, to the current test content.

Testing, log errors classification​

The possible errors detected in the status Behaviour Change, are now properly classified and enriched by all the details needed to investigate source root of the issue.

Testing, editing, baselines​

Baseline visualization has been updated optimizing the rendering per device.

Testing, editing, running​

Running a test directly into the editing mode has been improved, in particular the access to the results now available per device.

Testing, Trello integration​

In the brand configuration, it is now possible to enable the integration with Trello, for the automatic creation of tickets. In fact, once enabled, any ticket could also created in the Trello dashboard of preference.

Testing, edit, running option​

In order to enhance and facilitate the test creation, it is now possible run the test directly from the Editing panel and check instantly possible issues or positive results.

Testing, APIs & 3rd party services enhancement​

The status of each single request running in a page, now also affects the general status of the test. In fact, if any 3rd party or API request fails, it will be cause the application of API warning in the test status. It enhance the awareness of api status for any test validation.

Testing, easy popups management​

A new popup feature has been added to the automatic testing. It can be used anytime your ecommerce adopt popup strategies for cookies, newsletters, promotions. Sometimes they are triggered randomly and they can affect the proper test execution (break it because they can be unexpected). The idea, behind this new feature, is to add an action associated for each needed popup (close, accept, refuse, ...). In this way, everytime the popup will appear (anytime, anywhere in the running flow), in the test execution, it will be handled by the configured action.

Testing, auto detected issues​

The auto detection has been enhanced marking the test´s action as failure everytime an http error code is returned.

Testing, APIs & 3rd party services enhancement​

The status of each single request has been added in the API & 3rd party services: It has also been integrated in the browser console data of each test´s action.

Testing, Creation and editing​

The element creation for each testing action has been improved providing a better UX, in particular displaying the Xpath and better organizing all the elements of a test.

Testing, Dashboard​

The test running statistics have been separated into a drop down element. The focus has been defined in the immediate visualization of any possible issue or change found through the tests running.

Testing dashboard, update on main data visualization​

New widget added to the main testing dashboard ("Issues") and updated the data visualization of the testing results.

Testing dashboard, issues table​

A new table has been introduced in the main testing dashboard. It aims to summarized a list of the latest issues detected and associated tickets opened.

Ticket creation automation​

Rising an issue has been updated enhancing the data provided, automatically, to the same associated ticket. The issue reproduction test case, step by step, screenshots and browser console logs have will be now automatically added to the ticket.

API status validation​

New capabilities for the detection and visualization of all the API requests made by your ecommerce. Typical third party services and internal API calls are now kept under monitoring. For the main testing dashboard and the summary/details testing views, new APIs visualization status capabilities have been added.

Scheduled time for testing summary​

In the testing summary view a new feature has been introduced, allowing to review the status of the test throgh time, selecting the needed date with the help of a new select box.

Tests organization​

Introduced a better and usable visualization of the created tests.

Improved Generative AI capabilities​

For Web scores tool, we have been improved the Generative AI capabilities made it more smart to suggest better tips to fix issues reported by the audit.

SDK integration released in Beta​

Added full code capabilities. For the Quality Assurance testers, with programming experience, it will be easy to integrate their code repositories and check out the tests results directly in the Valido´s boards. In order to be integrated with Valido, the code tests should import and use the Valido´s SDK (still in beta). If interested, you can contact our support team: https://valido.ai/en/support/.

Read only mode for expired plans​

Even if your plan is over, now you could review the results (in read only mode) without any limitation, and eventually execute, edit or create a new test as soon as the plan is renewed or upgraded.

Self-service of plans updates​

Now you can upgrade & downgrade your plan whenever you need. You can even cancel it, without having the need to contact our support. Everything is self-service in order to provide full flexibility.

On-boarding directly form a URL​

You can on-boarding now providing, as initial step, directly the URL of your e-commerce. It will be connected to our website in order to facilitate the sign in and start using Valido as soon as possible.

Recorded sessions released!​

Added the no code capabilities. For the Quality Assurance testers, without programming experience, it will be one click away the creation of a functional test. Enabling the tracking code on the merchant website header, the real user sessions will be recorded and categorized in the "Recorded sessions" tab. Selecting a session, the test will be created click on "Create Test".

Improved visualization of the different types of tests​

The Tests tab, for the Testing tool, has been improved splitting the different types of tests in categories according to the way they have been created (manually or automatically with the recorded session feature).

Improved list of devices​

Available devices feature has been improved, on administration side, in order to allow a better a management of all the latest availabe devices.

Pricing and plans​

The plans have been extended with a better definition between free and paid plans. Details: https://valido.ai/en/pricing/.

How frequently should I visually test my ecommerce?​

Short answer: as much as you possibly can. Long answer: it depends. You should consider a minimum of once daily to a maximum frequency of every 15-30 mins.

What factors should I consider to decide the frequency of my visual tests?​

Let´s start from the scope / objectives of your ecommerce tests. There are 4 main ones to consider for any ecommerce (regardless of size):

1. Check that campaign & catalog changes have been applied as expected
2. Validate that the latest features have been deployed as expected
3. Review commerce platform configurations so that they are properly applied
4. Test the ecommerce customer flows and UX are working as expected

With all of the above objectives, you should consider how frequently your online business is updated, with respect to:

1. the catalog
2. the marketing content
3. the back-end code, the user interface (UI), and/or the customer experience (CX)
4. the various platform configurations (stock, shipping charges, jurisdictions, taxes, etc.)

Example 1: Test execution of once per day​

This frequency is appropriate for businesses which update their ecommerce less than once a week. These updates could be seasonal changes related to catalog and stock availability. The business may run a few campaigns per year, but configuration changes such as shipping, taxes, jurisdiction and the code are very rare. Generally the business has a stable ecommerce platform that is never under stress, and dependent on very few (if any) external services. Visual errors may cause high bounce rates and low conversion rates, however the business may deem it acceptable to be aware of such errors within 24 hours.

Example 2: Test execution every 6 hours​

This frequency is generally suitable for businesses which regularly update their online store, and also has a complex ecommerce infrastructure with coordination of external services. Continuous changes are made to the catalog and the stock availability. Frequent campaigns and marketing content updates are likely to involve changes to multiple web pages. The business may also need to update the store configuration and deploy new code at least once a month, possibly for multiple countries. There is an observable trend of visits and sales during the day.

An unexpected change or a UI/CX error can cause high bounce / low conversion rates, also eventually affecting the brand reputation. It is acceptable from the business standpoint to be aware of and to escalate the issue in less than 6 hours.

This test frequency usually requires a dedicated team to monitor Valido at least 8 hours a day, 7 days a week.

Example 3: Test execution every hour (or greater)​

This test frequency meets the demand of enterprise businesses which update their online store at a high frequency, due to its complex infrastructure, interactions with external services and integrations with best-of-breed applications. Continuous changes to the catalog and the stock availability are made by dedicated teams. Frequent campaigns and marketing content updates occur on different pages, across different languages and country sites. Continuous integration and continuous delivery (CI/CD) is a common practice, with the likelihood of weekly code deploys. There is a recognizable pattern of visits and sales throughout the day and the various periods of the year.

An unexpected change or a visual error causes high bounce / low conversion rate. The business deems brand trustworthiness and reputation as a key focus of its business, therefore UI/CX errors should be escalated ASAP.

This test frequency requires a dedicated team to monitor Valido 24 hours a day, 7 days a week.

How can Valido help?​

When you create a new test in Valido, the frequency appears in the configuration options:

However, creating and executing the test alone is not sufficient to meet your visual testing goals. You will also need to properly review the changes when Valido detect them. If you are unable to manage it all on your own, we at Valido can help you take care of it. In fact, we have a dedicated 24 x 7 support team that can handle the configuration, execution, and monitoring of your visual tests.

Are you interested? Contact us.