dhpe
Joined 14 years ago
Karma
77
Submissions
32
Member since
Dec 16
Recent submissions
Comment · 3 months ago
There's discussion whether this is a vuln. While some responsibility should be on the user to already having downloaded a malicious binary, I think it's poor default behavior from cursor to run git from the repo root. Is it really a use case to have git.exe in a git repo — more like a red flag.
Comment · 9 months ago
An Android app for CORE (YC S23) to make it as easy as possible to capture data to Core on-the-go. Voice-based UI, also quickly type in memories, and later retrieve by asking. https://memory2.app
Comment · 10 months ago
I have programmed 30K+ hours. Do LLMs make bad code: yes all the time (at the moment zero clue about good architecture). Are they still useful: yes, extremely so. The secret sauce is that you'd know exactly what to do without them.
Comment · 9 years ago
Comment · 9 years ago
I need to upload invoices every month from all ~20 SaaS products I subscribe to an accounting software. Most of the invoices can be just redirected from email to another SaaS that will let me download a zip file containing all invoices from a date range. Other software requires me to login to the product, navigate to a page and download a PDF or print an HTML page. I have browser-automated all of these laborious ones as well so everything will be in that zip file. Saves me 30 min monthly and especially saves me from the boring work.
Comment · 9 years ago
- Test cases should be designed to allow parallel execution (they should not interfere with each other)
- Do not use sleep() for synchronisation - use explicit waits (e.g. wait until element is visible, then proceed immediately)
Comment · 9 years ago
Really nice to have a generic functional interface to S3. Thanks.
Comment · 9 years ago
Thanks, good points. We have used ngrok for testing localhost. We actually wrote a helpful article on it. This is useful info regardless of the testing tool, so pasting it here: http://docs.usetrace.com/articles/connection/
Comment · 9 years ago
Thanks for the feedback. We have come quite far since last year. For example, now you can record html5 drag and drop events. Give it a try, we'd love to hear if there's a webpage with issues, so we can fix Usetrace.
Comment · 9 years ago
Having developed a test recorder, I found out that the best solution was to make mousehover an explicit action (the same as in webdriver). Better to have a robust test than try to do something too fancy.
Comment · 9 years ago
Since this thread hits my expertise... We have developed Usetrace (https://usetrace.com) for a few years targeting teams that want non-techies to automate GUI testing. (Disclaimer, I am a founder). So far the feedback has been positive and we're getting healthy revenue. It seems that teams are desperate for faster solutions than coded UI tests. But they will only use a tool that keeps up with frequent UI changes (automatically or semiautomatically) and is really painless and quick to use.
Some lessons learned that we're solving with the product:
- creating basic tests must be doable in 1 minute
- testing is a team effort (testers&devs) - must have collaboration tools built-in
- must be extendable with code (js)
- sync/timing issues must be handled automatically (when possible)
- UIs will change - generate locators and algorithms that adds robustness
- debugging must be speedy: must be able to debug test steps live with the browser context (html5 remote connection to the browser)
- randomness is needed - need an easy way to introduce random data (like random emails)
- testing emails must be as easy as testing a web page - inbox must be an integrated feature
- must handle frames transparently - user does not care if the element is inside a frame or not
- must be pluggable to CI
- must have good, clear reports
- some tests will be flaky - must be a way to keep builds stable & green
- no installations / plugins, just a browser
- fast to update tests when UI changes - the system must do global replacements when it sees duplicate stuff
- duplicate test step/code will cause a major maintenance burden - must have reusable/parameterizable components
- people will want to reuse functional tests for stress testing and monitoring - allow that too
- people need to check for dynamic content - must have a quick and codeless way to use variables
- people want to have quick builds - tool must offer parallel testing
- people will want to integrate to their own systems - must offer APIs
- html pages are responsive - must have support for different screen sizes
Twitter: https://twitter.com/dhpe
https://usetrace.com