Applitools Eyes ko Selenium Java test mein jodne ke liye Selenium se browser chalaiye, Eyes mein test kholiye, page par visual checkpoint lijiye, phir Maven se test run karke Applitools dashboard mein result dekhiye. Neeche ka workflow Applitools ke current Java Selenium quickstart aur maintained example par aadharit hai; vendor documentation English mein hai, isliye yeh Hindi mein samjhaya gaya tutorial hai, Applitools ka Hindi version nahin. Official Selenium Java quickstart aur example repository badal sakte hain, isliye code aur browser/grid options ke liye unke vartamaan nirdesh dekhein.
Applitools Eyes aur Selenium Java ka role
Selenium WebDriver browser ko kholta aur user-jaisi kriyaen karta hai. Applitools Eyes us browser state ka visual checkpoint leta hai aur use baseline se compare karta hai. Isse test sirf DOM ya text assertions tak seemit nahin rehta: screenshot mein layout, rang ya dikhne wale content ke badlav bhi pakde ja sakte hain. Ek batch test executions ko group karta hai, aur har eyes.check() ek visual test step hota hai.
Shuru karne se pehle kya chahiye
- Applitools account aur API key.
- JDK 8 ya usse naya.
- Maven; kuch IDEs mein Maven pehle se shamil hota hai.
- Up-to-date Chrome browser aur usi major version ka ChromeDriver.
- Basic Java aur Selenium ki samajh.
Java, Chrome aur driver compatibility samay ke saath badal sakti hai. Agar driver startup fail ho, to apne Selenium version ke driver-installation nirdesh aur Chrome/ChromeDriver major versions dobara milaiye. Applitools ki prerequisite list quickstart mein hai.
API key ko surakshit tareeke se set karein
Key ko source code mein hard-code ya public repository mein commit na karein. Use process environment mein APPLITOOLS_API_KEY naam se dein, ya IDE ki run configuration mein environment variable set karein. Shell mein udaharan:
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
export APPLITOOLS_API_KEY="YOUR_API_KEY"Windows PowerShell mein vartamaan terminal session ke liye:
$env:APPLITOOLS_API_KEY="YOUR_API_KEY"YOUR_API_KEY ko apni asli key se badlein; ise kisi ko dikhane wale code snippet ya log mein na rakhein. IDE se test chalate waqt bhi wahi variable test process ke environment mein hona chahiye.
Rank #2
Maintained Java example clone karke chalayein
Current quickstart purane snippets ke bajay maintained example repository se shuru karata hai. Repository clone karein aur project dependencies install karein:
git clone https://github.com/applitools/example-selenium-java-basic.git
cd example-selenium-java-basic
mvn installInstall poora hone par quickstart ka test command chalayein:
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesmvn exec:exec@run-the-tests -Dexec.classpathScope=testCommand ko project ke root folder se run karein. Repository ki current source files ko code ke liye authoritative maanein; yahan purane checkWindow API wale snippets jaan-boojhkar nahin diye gaye, kyunki woh alag, legacy API shape hai.
Sample test mein kya hota hai
Maintained sample VisualGridRunner, configuration object, ChromeOptions aur Selenium WebDriver ka upyog karta hai. Uska flow samajhne ke liye ye steps dekhein:
- Runner aur configuration: Visual Grid runner aur Eyes configuration banayein; configuration mein batch/test jaise pahchan dene wale naam aur zaroori browser/device targets rakhe jaate hain.
- Browser taiyar karein:
ChromeOptionsconfigure karke SeleniumWebDriverse browser session shuru hota hai. - Eyes test kholein:
eyes.open(...)mein driver aur test/page ki pahchan dekar visual test shuru karein. - Page par jaayein: WebDriver se target URL kholein aur zaroori UI actions karein, taaki checkpoint us state ko capture kare jo test karni hai.
- Visual checkpoint lein:
eyes.check(...)page ya chune hue region ka visual test step banata hai. - Cleanup karein: Test lifecycle ke mutabik Eyes ko close karein aur browser/runner resources band karein, taaki session khula na chhoote.
Method signatures, imports aur cleanup ka sahi roop SDK version ke saath badal sakta hai; poora runnable implementation maintained example repository se lein, na ki kisi purane tutorial se. Quickstart example Ultrafast Grid ke browser/device targets configure karta hai. Yeh sample configuration hai, har account ke access ya target catalog ki guarantee nahin; chalane se pehle current vendor quickstart mein uplabdh targets dekhein.
Pehela run aur Applitools results samjhein
Maven command ke baad dashboard mein batch ke andar test execution aur uske visual checkpoints dekhein. Agar pehli baar us test ka baseline nahin hai, to run New dikh sakta hai aur baseline save hota hai. Baad ke run mein image baseline se alag ho to result Unresolved ho sakta hai; checkpoint image dekhkar tay karein ki badlav ichchhit hai ya regression. Baseline ko bina jaanch accept karna visual test ko kam upyogi bana sakta hai.
Match level sahi chunna
Match level tay karta hai ki visual comparison kis tarah ke badlav ko mahatva dega. Quickstart Strict ko default batata hai; dynamic region ke liye kam sakht mode chunna ek jaan-boojhkar kiya gaya trade-off hona chahiye.
| Match level | Kya nazar aata hai | Kab vichaar karein |
|---|---|---|
| Strict | Quickstart ke anusaar human-visible visual differences; yahi default hai. | Jab region ka expected appearance sthir ho aur aam visual badlav bhi review karne hon. |
| Ignore Colors | Rang ke badlav nazarandaz hote hain; structure/content ke badlav compare hote hain. | Jab rang jaan-boojhkar badal sakte hon, par baaki visual sanrachna mahatvapurn ho. |
| Layout | Overall structure aur relative positioning check karta hai; quickstart ke example mein dynamic content ko ignore karta hai. | Dashboard ke aise chuninda elements ke liye jahan content badalta rahta hai, par layout mahatvapurn hai. |
Quickstart chune hue CSS selectors par .layout(...) lagane ka udaharan deta hai. Iska uddeshya sirf wahi dynamic region alag se match karna hai; unexplained visual changes ko chhupane ke liye poore page ko loose match level na dein. Exact selector syntax aur vartamaan API usage quickstart mein dekhein.
Common problems aur unke hal
- API key missing ya Eyes authentication fail: Check karein ki
APPLITOOLS_API_KEYusi shell/IDE run configuration mein set hai jahan se Maven test chal raha hai; key ko code mein daalne ke bajay process environment mein dein. - Maven dependency ya build error: Project root mein hone ki pushti karein, phir
mvn installpoora hone dein. Error ke mutabik Maven output mein pehli failing dependency ya compilation line dekhein. - ChromeDriver start nahin hota: Driver executable ki availability/installation jaanchein aur Chrome aur ChromeDriver ke major versions ko align karein.
- Grid target ya configuration kaam nahin karta: Sample mein diya target har account mein uplabdh hoga, yeh maan kar na chalein. Current target catalog aur account access vendor documentation mein verify karein.
- Baad ka run Unresolved dikhata hai: Checkpoint image ko baseline ke saath compare karein. Agar badlav sahi hai tabhi review ke baad baseline update karein; agar nahin, page styling, browser state aur test setup investigate karein.
Or skip the browser setup
Agar aapko apne Java/Selenium flow mein visual assertion ke bajay ek website screenshot chahiye, ScreenshotNeo ek website screenshot API aur MCP server hai. Iska ek GET request URL se PNG, JPEG, WebP ya PDF deta hai; yeh Applitools baseline comparison ka badal nahin hai. API options aur parameters ke liye ScreenshotNeo docs dekhein.
Quick Recap
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo capture se pehle cookie/consent banner accept karta hai aur 60 se zyada jaane-pehchaane consent platforms, newsletter popups aur chat widgets hata sakta hai; har step band kiya ja sakta hai. Bot checks/CAPTCHAs, blank pages, timeouts, failed loads aur cache hits par charge nahin lagta, aur response X-Page-Verdict aur X-Billed headers se status batata hai. Claude, Cursor aur kisi bhi MCP client ke liye take_screenshot, get_page_info aur capture_pdf tools wala MCP server bhi hai. Free plan mein bina card ke 1,000 screenshots/month hain; paid plans $5 mein 3,000 se shuru hote hain. ScreenshotNeo par sign up karein aur 1,000 free screenshots/month bina card ke paayein.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
