Question 1

Qu'est-ce que le test de régression visuelle ?

Accepted Answer

Visual regression testing is an automated way to detect unintended UI changes by comparing a baseline screenshot to a current screenshot after a deployment or code change. In ScanU, each run captures screenshots across selected pages, browsers, and device presets, then highlights visual differences so teams can review layout shifts, missing elements, spacing issues, font changes, and color drift before users notice them. This workflow is especially useful for frontend teams shipping frequently, because automated visual testing catches issues that unit tests and API tests cannot see. In practice, ScanU works as a screenshot comparison tool for UI regression testing: your first approved run becomes the baseline screenshot comparison reference, and later runs are measured against it. You can tune diff thresholds to reduce noise from small rendering variations while still detecting real regressions. The result is faster visual bug detection and more confidence in every release.

Question 2

Comment démarrer avec ScanU ?

Accepted Answer

Getting started with ScanU is designed to be no setup and low friction. First, create an account and add a project with a publicly reachable URL. Next, run your first scan and choose the pages, browsers, and device presets you want to cover. That first successful run acts as your baseline, which means future runs can perform baseline vs current screenshot comparison automatically. After that, your workflow is simple: trigger another run after product updates, review visual diffs, and approve intentional changes when needed. This gives you a repeatable automated visual testing process without building your own image infrastructure. For teams exploring visual regression testing with Playwright, ScanU can complement existing test suites by adding managed screenshot diff reporting and historical run tracking. If you are new to cross browser testing, start with core user journeys first, then expand coverage incrementally as your release process matures.

Question 3

Dois-je installer quelque chose ?

Accepted Answer

No. ScanU is a cloud-based visual regression testing platform, so you do not need to install browsers, diff tooling, or screenshot storage infrastructure to begin. You can sign in, configure a project, and start running automated screenshot comparisons directly from the dashboard. This is one reason teams choose ScanU as a no-install screenshot comparison tool when they want faster onboarding and predictable execution environments. If your team already uses local Playwright tests, you can still keep that setup for component or end-to-end checks and use ScanU for managed baseline screenshot comparison and centralized review. The key point is that ScanU itself does not require a local agent for core usage on public URLs. You only need a modern browser to access the app. This approach reduces setup complexity, shortens time-to-value, and helps teams implement visual bug detection without maintaining additional infrastructure.

Question 4

Quel type de sites web puis-je tester ?

Accepted Answer

ScanU supports visual regression testing for publicly accessible websites and web applications that can be reached from the public internet. That includes production sites, preview environments, and staging URLs, as long as they are externally reachable. Teams commonly use this for marketing pages, SaaS dashboards, and responsive web apps where cross browser layout testing and screenshot diff quality are critical. For security reasons, ScanU does not test localhost, internal network targets, or private IP ranges. This restriction protects the platform against SSRF-style abuse and keeps scanning boundaries clear. If your staging environment is private, publish a controlled public preview URL before running checks. Also note that dynamic pages with rapidly changing content may require careful threshold tuning to avoid unnecessary noise. In short: if a page is public and stable enough to compare, it is a good fit for baseline screenshot comparison in ScanU.

Question 5

Quels navigateurs sont pris en charge ?

Accepted Answer

ScanU currently supports the three Playwright browser engines: Chromium, Firefox, and WebKit. That gives teams practical cross browser visual testing coverage for the majority of modern user traffic while keeping runs consistent and repeatable. Because rendering engines differ in font rasterization, anti-aliasing, and CSS behavior, running across all three browsers is a reliable way to catch regressions that only appear in one environment. Each browser run has its own baseline comparison context, so you compare Chromium-to-Chromium, Firefox-to-Firefox, and WebKit-to-WebKit across time. This avoids false conclusions from comparing different engines directly. For SEO relevance and real QA value, this is where automated visual testing intersects with cross browser compatibility: you can validate that key pages look correct in multiple rendering engines before release. If needed, start with one browser for speed and expand to full coverage as your release cadence and risk profile require.

Question 6

Quels appareils puis-je tester ?

Accepted Answer

ScanU provides a curated library of device presets so you can run cross device testing without manually defining every viewport. Presets cover mobile, tablet, laptop, and desktop resolutions, helping teams validate responsive behavior with the same baseline screenshot comparison workflow used for browser coverage. This is especially useful when debugging layout bugs that only appear at specific widths or device classes. The exact number of available presets depends on your plan: Free (10), Pro (35), Pro+ (70), and Max (98). In all cases, the idea is consistent: select relevant breakpoints, run automated visual testing, and review diffs by page and viewport. For teams focused on responsive QA, a smaller preset set can validate critical paths quickly, while larger tiers allow broader cross device testing across more real-world screen sizes.

Question 7

Comment fonctionne la découverte de pages ?

Accepted Answer

Page discovery helps you scale visual regression testing beyond a single URL. After you enter a website address, ScanU crawls reachable pages and returns candidates you can include in a scan. You stay in control: discovery proposes coverage, and you decide which pages are part of your automated visual testing scope. This approach is useful for large marketing sites or multi-section apps where manual URL entry is slow. Plan limits apply per crawl session: Free supports up to 100 pages, while paid tiers support 300 to 1000. Once selected, discovered pages follow the same baseline screenshot comparison workflow as manually added pages. In practice, teams often combine top-converting pages, critical flows, and template-driven pages for efficient visual bug detection. Discovery accelerates setup, while targeted selection keeps screenshot credits focused on high-impact coverage.

Question 8

Où sont stockées mes données ?

Accepted Answer

ScanU stores customer data in Frankfurt, Germany on EU-based infrastructure. That includes screenshots, diff outputs, and related run metadata used for automated visual testing workflows. Keeping data residency in the EU helps teams satisfy internal compliance expectations and supports GDPR-aligned operations for organizations that need regional processing boundaries. From an operational perspective, storing baseline and current screenshots in one controlled region improves consistency and simplifies access auditing. This matters when teams rely on historical baseline screenshot comparison for release reviews or incident investigations. We do not claim global region replication for customer data in this workflow; the service is intentionally centered on EU hosting. If your legal or procurement team needs details for security review, contact support for current documentation so your policy checks map to the latest platform implementation.

Question 9

Combien de temps les captures d'écran sont-elles conservées ?

Accepted Answer

Screenshot retention is plan-based and determines how long baseline and historical run images remain available for visual regression testing review. Current retention windows are: Free (3 days), Pro (15 days), Pro+ (30 days), and Max (90 days). After the retention period expires, screenshots are automatically removed according to platform policy. Retention impacts how far back you can investigate visual changes, compare release periods, and reference older baseline screenshot comparison states. If your team needs longer audit trails for QA or compliance, choose a tier with a longer retention window and export critical evidence when needed. For day-to-day UI regression testing, many teams pair scheduled scans with retention-aware workflows so they always keep fresh baselines and recent history. This creates a practical balance between storage control, review depth, and reliable visual bug detection across ongoing releases.

Question 10

Mes données sont-elles sécurisées ?

Accepted Answer

Security is built into ScanU's visual testing platform operations. Data is protected in transit with HTTPS and protected at rest using managed encryption controls. Access to authenticated functionality is token-based, and platform protections such as rate limiting and SSRF defenses reduce abuse risk in the screenshot capture pipeline. These controls are important for teams running automated visual testing on external URLs and storing comparison artifacts over time. Security also includes sensible product boundaries: private-network targets are not supported, which reduces the attack surface for crawler and rendering infrastructure. On the user side, account security depends on responsible credential handling and least-privilege practices for shared team access. While no SaaS platform can claim absolute risk elimination, ScanU is designed for practical, modern web security expectations around screenshot comparison workflows. If you need formal documentation for vendor review, contact us for the latest policy and architectural details aligned to current deployment practices.

Question 11

Puis-je exporter mes données ?

Accepted Answer

Yes. You can request export support for your ScanU account data, including project configuration and run-related metadata needed for operational continuity or compliance workflows. Export availability helps teams preserve evidence from visual regression testing, transition between tools, or satisfy GDPR data portability requirements. Because visual testing datasets can be large, export scope may vary based on what is required for your use case—for example, metadata-only extracts versus broader run history. If your team needs a specific format for internal reporting, mention that in your request so support can guide the most practical path. For recurring governance needs, many teams pair retention settings with periodic exports to keep critical baseline comparison records outside the platform as well. Contact hello@scanyou.eu to initiate a request and include your account details so we can process it efficiently and securely.

Question 12

Puis-je supprimer mon compte ?

Accepted Answer

Yes. You can delete your ScanU account from settings, and deletion is intended to remove associated project data, run history, screenshots, and comparison artifacts. This gives users direct control over lifecycle management of visual regression testing data and supports privacy-first operations when a workspace is no longer needed. Because deletion is irreversible, we recommend exporting any required audit information before confirming the action. That includes baseline screenshot comparison records you might need for post-release review, incident documentation, or compliance reporting. For teams, it is best to coordinate deletion with project owners so no active workflows are interrupted unexpectedly. If you are unsure whether full account deletion is necessary, consider first reducing retention scope or removing specific projects. When deletion is confirmed, the goal is complete removal of account-linked data according to current platform policy.

Question 13

Que sont les crédits de capture d'écran ?

Accepted Answer

Screenshot credits are the usage unit behind each scan. In ScanU, one captured screenshot consumes one credit, and total usage is calculated as pages × devices × browsers for each run. For example, testing 5 pages on 2 devices in 3 browsers uses 30 screenshot credits. This transparent model helps teams estimate cost for automated visual testing before they scale coverage. Credits map directly to baseline screenshot comparison volume, so optimization is straightforward: prioritize critical pages, right-size device coverage, and run full suites when release risk is highest. Teams often keep a lean daily suite and a broader pre-release suite to balance confidence and budget. Understanding credit math also helps when planning cross browser testing and responsive checks across multiple breakpoints. If you are just starting, run a small pilot first, measure consumption, and then expand your UI regression testing strategy with predictable monthly usage.

Question 14

Existe-t-il une offre gratuite ?

Accepted Answer

Yes. ScanU includes a free tier so teams can evaluate visual regression testing workflows without upfront commitment. The free plan includes 1 project, 500 screenshot credits per month, All 3 browsers, 10 devices, 3-day retention, and page discovery up to 100 pages per crawl. No credit card is required to start. This makes the free tier useful for validating baseline screenshot comparison on core pages, testing your review process, and estimating future cross browser testing needs. It is especially practical for freelancers, early-stage teams, or engineering groups piloting automated visual testing before broader rollout. As coverage grows, upgrading unlocks more credits, more devices, and longer retention windows. A common path is to prove value on critical journeys first, then scale to wider site coverage once your team has established a repeatable visual bug detection process.

Question 15

Quelles sont les options d'offres payantes ?

Accepted Answer

ScanU offers three paid tiers for teams that need broader coverage, higher screenshot volume, and longer retention for historical review. Pro (€19/month) includes 5 projects and 3,000 credits monthly. Pro+ (€29/month) increases limits to 10 projects and 10,000 credits. Max (€49/month) is designed for larger workloads with 20 projects and 50,000 credits per month. Each tier also expands device access and retention windows, which directly impacts how deeply you can run cross device testing and long-term baseline screenshot comparison. Choose based on release frequency, number of critical pages, and how many browser/device combinations you want per run. If your team is implementing visual testing in CI/CD, estimate monthly run volume first so your plan supports both routine checks and peak release periods without constant limit management.

Question 16

Puis-je annuler mon abonnement à tout moment ?

Accepted Answer

Yes. You can cancel from the billing area at any time. When cancelled, paid access remains active through the end of the current billing cycle and then transitions to the Free tier automatically. This gives teams predictable account behavior and avoids sudden disruption in active visual regression testing workflows. Before cancellation takes effect, review your retention window and export any baseline screenshot comparison history you may need for internal records. If your team depends on higher-tier limits for cross browser testing or broader page coverage, plan a reduced suite that fits Free-tier limits so monitoring continuity is maintained after downgrade. There are no cancellation penalties, which makes ScanU practical for seasonal usage or project-based needs. In short, you keep control over subscription timing while preserving service access through the prepaid period.

Question 17

Proposez-vous des remboursements ?

Accepted Answer

ScanU provides a 14-day money-back guarantee for first paid subscription purchases. If the service is not the right fit, contact support within that window and we will review your request for a full refund under the current policy. This trial-style safeguard helps teams evaluate automated visual testing workflows with lower financial risk. To speed processing, include billing email, workspace details, and payment date in your request. We also recommend exporting any data you want to keep before account changes, especially if you created baseline screenshot comparison history during evaluation. Refund policy scope and timing are applied according to current terms, so if your procurement team needs formal language, request the latest policy text from support. The core goal is straightforward: you can test ScanU in real project conditions and decide with confidence before long-term commitment.

Question 18

Les prix sont-ils en EUR ?

Accepted Answer

Yes. All public ScanU pricing is listed in EUR. For EU customers, VAT may apply depending on billing country and tax status, and final tax amounts are calculated during checkout. Keeping pricing in a single currency simplifies budgeting for teams planning recurring visual regression testing costs across projects. When estimating spend, combine subscription cost with expected screenshot credit usage based on your baseline comparison scope: number of pages, browsers, and devices per run multiplied by run frequency. This gives a realistic monthly estimate for automated visual testing and cross browser layout coverage. If your organization requires specific invoicing details or VAT handling confirmation, contact support before purchase so finance workflows are aligned. Transparent billing in EUR plus predictable usage modeling helps teams adopt visual QA with fewer procurement surprises.

Question 19

Puis-je tester des environnements localhost ou de staging ?

Accepted Answer

ScanU does not support localhost, private IP addresses, or internal-only hosts. This is an intentional security control to reduce SSRF risk in a cloud screenshot environment. You can, however, test staging or preview environments if they are publicly reachable over the internet. For many teams, this is enough to run baseline screenshot comparison before production deployments. If your staging stack is private by default, expose a controlled public preview URL for the pages you want to validate. Then run automated visual testing on that endpoint with the same browsers and device presets you use in production checks. This workflow preserves security boundaries while still enabling cross browser visual testing and release gating. In short: public URL required, private-network scanning blocked by design.

Question 20

Comment fonctionne le seuil de diff ?

Accepted Answer

Diff threshold controls sensitivity in screenshot comparison. It defines how much visual change is required before a result is flagged as a regression. Lower thresholds catch even small pixel shifts; higher thresholds reduce noise from minor rendering differences such as anti-aliasing or subtle font rasterization changes. This is essential for practical automated visual testing at scale. A good starting point is conservative: keep threshold strict for stable, design-critical pages and slightly relax it for dynamic or animation-heavy views. The goal is not to hide real issues, but to separate meaningful UI regressions from technical noise. In baseline vs current screenshot comparison workflows, threshold tuning is one of the highest-impact settings for review efficiency. Teams that calibrate thresholds per project usually get faster triage, fewer false positives, and better confidence in visual bug detection across browsers and device presets.

Question 21

Existe-t-il une API pour l'intégration CI/CD ?

Accepted Answer

Yes. ScanU supports API-driven workflows so teams can integrate visual testing in CI/CD pipelines and automate scan orchestration. You can create project API keys, trigger runs, and retrieve scan status and diff outputs through documented endpoints. This enables pull-request checks and release-gate automation around baseline screenshot comparison. For teams using visual regression testing with Playwright, the common pattern is: run your app build in CI, trigger ScanU scans for key URLs, then fail or warn the pipeline based on detected regressions. This blends code-level tests with cross browser visual testing in one release workflow. Keep in mind that practical setup still requires secret management, stable test data, and clear approval rules for intentional UI changes. The API provides the automation layer; your team's review policy determines how strict enforcement should be in production pipelines.

Question 22

Comment gérer le contenu dynamique ?

Accepted Answer

Dynamic content is the main source of noise in visual regression testing, so stabilization strategy matters. Start by making pages as deterministic as possible during capture: use fixed demo data where practical, disable rotating banners if possible, and avoid timestamps that change on every request. Then tune threshold settings so minor expected variation does not overwhelm reviewers. In ScanU, teams often combine controlled test pages with selective coverage of high-value flows to keep automated screenshot diff results actionable. If a page remains highly dynamic, treat it as a lower-signal check and focus strict baseline screenshot comparison on stable layouts. The objective is to maximize true visual bug detection while minimizing false positives. Over time, document which pages are stable, semi-stable, or noisy, and align your cross browser testing expectations accordingly. Stable inputs plus calibrated thresholds create the most reliable UI regression testing pipeline.

Question 23

Que se passe-t-il si un test échoue ?

Accepted Answer

When a ScanU run fails to complete, the run details include error context so your team can troubleshoot quickly. Common failure causes include destination timeouts, SSL certificate issues, redirect loops, and temporary availability problems on the target site. These are execution failures, not visual diffs, and should be resolved before interpreting regression status. Once the issue is fixed, rerun the scan to restore baseline comparison continuity. In day-to-day operations, teams treat failures as signal about environment reliability: if failures are frequent, improve staging stability and deployment timing before tightening visual testing gates. Distinguishing "run failed" from "visual diff detected" is important for CI/CD workflows, because the remediation path differs. Execution failures require infrastructure troubleshooting; diff failures require UI review. ScanU surfaces both so teams can protect release quality with clear, actionable feedback.

Foire aux questions

Premiers pas

Navigateurs et appareils

Données et confidentialité

Tarifs et facturation

Technique

Vous avez encore des questions ?

Prêt à essayer ScanU ?