dhpe

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.

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

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.

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.

- 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)

Really nice to have a generic functional interface to S3. Thanks.

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/

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.

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.

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

Thanks, this is useful.

My startup http://usetrace.com is a web monitoring (+regression testing) tool with the "monitor for your users" philosophy mentioned in Rob's article. Monitoring is done on the application/feature level -> alerts are always about a feature visible to the users.

Some improvements made. Going to be better!

You can add coded steps when you need advanced features. You'll have javascript in your site's context available.

We're currently providing a way to reuse the beginning of trace in other traces. Most traces start with logging in to the app, so you can create the login trace, and share it to all other traces. So you end up defining signing up once.

Hi, thanks for the awesome feedback!

About pricing, you can test all features for free. If you like it and continue to use it, you can subscribe to one of our plans.

Copy pasting is a feature which we haven't solved yet. It would definitely be a huge productivity boost when making traces.

Console output is in our backlog but currently we focus on more important issues.

Most of the teams do not have required skills for scripted test automation. Even the teams that do have the skills struggle to have time for testing.

Personally after doing programmed Selenium tests for 9 years, I have learned that when releasing software daily, scripted tests lag all the time behind development. Providing a simplified testing tool that allows easy trace creation and maintenance without programming is needed.

However traditional record & playback tools are not working for agile teams due to maintenance burden. Usetrace brings concepts from the scripted testing available to non-programmers.

1. Just click "Run Trace" to verify the automation works.

2. Yes, from Dashboard it's currently FF&Chrome only, but via API you can include IEs. I can help you to get started (mailto arto@usetrace.com)

3. If a Trace can be walked through it passes. A Trace includes steps like clicks on buttons and checks (explicit things that must be visible on the page, e.g. text or other elements).

Thanks! We're going to improve the landingpage. Meanwhile, check out this video: https://www.youtube.com/watch?v=ZQqAr4jJ9Xw - signing up is also free.

Thanks, a good point!

I'm working on a visual web testing automation tool Usetrace (http://usetrace.com).

Our QA process is relying on it.

We're:

- automatically checking our most critical features every time our code changes in our QA environment

- monitoring the end user experience on production environment using the same automated tests every minute

- creating and maintaining the tests with our tool

- getting live feedback to our development team's flowdock chat through our own APIs

One of the biggest obstacles in web test automation is the pain of test case maintenance.

A record/replay solutions have been attempted by many. Unfortunately they don't work.

Usetrace instead ties the code editor and the product under test together and provides a powerful interactive IDE for software developers.

Unlike our competitors we provide everything needed in UI testing in one package and it requires no installations.

Tests are written, maintained and executed in Usetrace using Python/Webdriver.

We're a Helsinki based startup and we'd love to hear your feedback!