You will get I will convert your web app pricing workflow to CSV or Excel
Project details
Send me your client-provided pricing workflow; I will return a clean CSV, JSON, or Excel-ready report from the permissioned path.
You get structured output, validation notes, and clear rerun steps.
Good fits include quote calculators you own, authenticated internal tools, product option flows, repeated form inputs, and web-app tables where you need report-ready rows.
My approach is to confirm your permission and exact output fields, map one approved workflow path, add stable waits and validation checks, then return clean files with run notes, screenshots/logs, and known edge cases.
I do not bypass CAPTCHA, protection, paywalls, access controls, or site terms. I work only on systems you own, manage, or have permission to use. Use safe temporary or collaborator access through approved channels.
Delivery times shown are safe estimates - I often deliver faster. The clock starts once requirements and access are available.
Related proof sample: I maintain a public Playwright reliability demo showing how I turn timing-sensitive browser workflows into repeatable, documented, CI-checked automation.
You get structured output, validation notes, and clear rerun steps.
Good fits include quote calculators you own, authenticated internal tools, product option flows, repeated form inputs, and web-app tables where you need report-ready rows.
My approach is to confirm your permission and exact output fields, map one approved workflow path, add stable waits and validation checks, then return clean files with run notes, screenshots/logs, and known edge cases.
I do not bypass CAPTCHA, protection, paywalls, access controls, or site terms. I work only on systems you own, manage, or have permission to use. Use safe temporary or collaborator access through approved channels.
Delivery times shown are safe estimates - I often deliver faster. The clock starts once requirements and access are available.
Related proof sample: I maintain a public Playwright reliability demo showing how I turn timing-sensitive browser workflows into repeatable, documented, CI-checked automation.
Programming Languages
JavaScript, Python, TypeScriptCoding Expertise
Cross Browser & Device CompatibilityWhat's included
| Service Tiers |
Starter
$175
|
Standard
$700
|
Advanced
$1,400
|
|---|---|---|---|
| Delivery Time | 2 days | 6 days | 10 days |
Number of Revisions | 0 | 0 | 0 |
Number of Pages Mined/Scraped | 1 | 10 | 25 |
Number of Sources Mined/Scraped | 1 | 1 | 1 |
Install Script | - | - | - |
Test Script | - | - | - |
Task Automation | - | - | - |
Frequently asked questions
About Jonathan
Senior QA & Browser Automation Engineer | Playwright, Selenium, Python
Tel Aviv, Israel - 6:52 am local time
What I can help you with:
• Playwright / Selenium framework design or repair — built from scratch or rescued from flakiness
• Flaky-test stabilization — turn random failures into diagnosable ones with traces, screenshots, retries, and stable selectors
• Python automation & web scraping / data pipelines — reliable, logged, maintainable
• CI browser checks — tests that actually run green in CI, not just on your laptop
• Secondary: API/webhook integrations and n8n/Make/Zapier workflow automation
A recent build: a Playwright + MCP system that lets developers write tests far more easily — the kind of reliability tooling I specialize in. At Motorola I owned automated performance/benchmark testing for the LEX 700 (Android) and was the automation focal point for two worldwide teams.
How I work: I start with one narrow, paid first milestone and clear success criteria — one stabilized test path or one working automation, with logging, failure evidence, and handoff notes — then expand once you've seen it work. I'm newer to Upwork than
to automation engineering, so I keep the first step small and low-risk on purpose.
Send me the workflow or the failing test and I'll propose the smallest useful first milestone.
Recent proof: I published a Playwright flaky-test repair demo with a real before/after measurement - the flaky checkout suite passed 17/20 local runs, while the stabilized suite passed 20/20 with CI proof (see Portfolio).
Steps for completing your project
After purchasing the project, send requirements so Jonathan can start the project.
Delivery time starts when Jonathan receives requirements from you.
Jonathan works on your project following the steps below.
Revisions may occur after the delivery date.
Define inputs and fields
We confirm the calculator/workflow, allowed access, sample inputs, and expected output fields.
Map the browser path
I build the first reliable run with stable selectors, waits, and stop conditions.