lucgagan

I have never needed to use 95% of these extensions. Why would someone want to install all of them by default? Update nightmare.

This title makes little sense

After identifying a gap in the availability of a single, exhaustive reference for software testing terms, I took it upon myself to bridge this gap. I've put together what I consider to be the most in-depth glossary on this topic, with help from both ChatGPT and my own insights. I present this to the HackerNews community, inviting you all to contribute and further enrich it.

https://ray.run/glossary

To ensure the resource remains dynamic and ever-evolving, there's a "Was this helpful?" form embedded for your feedback. Our collective expertise can transform this glossary into the ultimate, go-to guide. Whether you peruse all the terms or just a few, your perspective might spot areas of improvement or enhancement.

Upcoming features:

* Wikipedia links for each term.

* Inclusion of synonyms.

* Categorization tags for terms (like automated testing vs. manual testing).

* Definitions via hover-over on https://ray.run/blog articles mentioning these terms.

Looking forward to your feedback and insights. Let's make this a collaborative effort!

This may sound dumb, but I never trusted microwaves. It just feels so unnatural. I even have basic understanding on how they work (water molecules in food start to vibrate producing heat), but it just doesn't taste good and feels off. No way it is healthy.

Can we not derive this information by looking at adoption of these APIs across the web?

Been following your story on Twitter for a long time. Very inspiring. I really like the DevUtils app that you built. You never mention what MRR it is generating today, though. Would love to know if you managed to grow it to anything of meaningful MRR.

That is very cool and much needed, but I am _paranoid_ about hosting the data myself. I've lost too many databases over the years to the most random mistakes. Granted, technology has matured a lot over the last decode, but still... the cost (the nights spent debugging and troubleshooting) of maintaining the database yourself is just not worth it when managed solutions exist.

Somewhat to my surprise, these appear to be getting very little traffic

https://www.similarweb.com/website/devurls.com/#ranking

although I don't know how similarweb gets its data

This is very neat. I found a new homepage to use it seems!

"Unlimited" positioning rubs me the wrong way. It really means "until we deem to be no longer reasonable for personal use".

Can you delve a bit deeper into how WASM works? Specifically, how heavy is the WASM module? Also, is there a specific use-case you've seen where this shines particularly brightly?

Hello HN,

After grappling with the frustrations of manually styling long bash commands for over a decade, I finally created a tool to automate it. The motivation was simple: most DevOps professionals, like myself, document their commands. When tutorials or services (take Google Cloud Platform for instance) provide long commands on a single line, it's a legibility nightmare.

Example from GCP:

    gcloud beta container --project "rayrun" node-pools create "test-runners-1" --cluster "rayrun" --zone "us-central1-c" --machine-type "e2-medium" --image-type "COS_CONTAINERD" --disk-type "pd-balanced" --disk-size "100" --metadata disable-legacy-endpoints=true --scopes "https://www.googleapis.com/auth/devstorage.read_only","https://www.googleapis.com/auth/logging.write","https://www.googleapis.com/auth/monitoring","https://www.googleapis.com/auth/servicecontrol","https://www.googleapis.com/auth/service.management.readonly","https://www.googleapis.com/auth/trace.append" --num-nodes "3" --enable-autoupgrade --enable-autorepair --max-surge-upgrade 1 --max-unavailable-upgrade 0

After spending far too much time manually adding line breaks and styling, it would look like:

    gcloud beta container \
      --project "rayrun" \
      node-pools create "test-runners-1" \
      --cluster "rayrun" \
      --zone "us-central1-c" \
      --machine-type "e2-medium" \
      --image-type "COS_CONTAINERD" \
      --disk-type "pd-balanced" \
      --disk-size "100" \
      --metadata disable-legacy-endpoints=true \
      --scopes "https://www.googleapis.com/auth/devstorage.read_only","https://www.googleapis.com/auth/logging.write","https://www.googleapis.com/auth/monitoring","https://www.googleapis.com/auth/servicecontrol","https://www.googleapis.com/auth/service.management.readonly","https://www.googleapis.com/auth/trace.append" \
      --num-nodes "3" \
      --enable-autoupgrade \
      --enable-autorepair \
      --max-surge-upgrade 1 \
      --max-unavailable-upgrade 0

This might seem trivial for one-off commands, but it quickly becomes a tedious chore with frequent DevOps tasks.

In light of this, I introduce to you, the *Bash Command Prettifier*.

All you have to do is input your lengthy bash command, and the script will automatically format it with a neat line-break after every parameter, making it easily readable and perfect for documentation.

The code is available as an open-source gist here: Bash Command Prettifier (https://gist.github.com/lucgagan/9f4219058f89c9d003ceced6d1d...)

Would love feedback, improvements, or any thoughts. If this has been a pain point for you too, hope this helps ease your DevOps documentation woes!

Test it online: https://ray.run/tools/bash-command-formatter

It does indeed.

I like your idea of suggesting multiple selectors. Don't know how that didn't cross my mind.

But in short, I am trying to generate selectors that would rely on the contents rather than attributes (like CSS).

I am also trying to detect selectors that are generated vs manually typed (i.e. likely to remain static vs generated).

Just heads up that the version that is approved by Google Chrome Store does not include all the latest changes. I've made a ton of improvements to this over the last two days, and they take quite a while to review.

I am also going to make this open-source as a separate package.

Site is down (I am learning some hard life lesons about DNSSEC)

Here is a direct link:

https://chrome.google.com/webstore/detail/rayrun/olljocejdge...

Site is down (I am learning some hard life lesons about DNSSEC)

Here is a direct link:

https://chrome.google.com/webstore/detail/rayrun/olljocejdge...

I just meant to break the silence :facepalm:

For Playwright, it'd do pretty well. For xpath, I will need to build a few examples. I will update documentation to include a few of these examples.

It is not better, it is just accessible from a different location (your browser extension) vs Playwright's debugger. This falls more naturally into my development flow.

Hello, fellow hackers!

3rd attempt to posting something to ShowHN. Learning from my mistakes (and hopefully not making new ones).

I'm excited to introduce you to Rayrun extension - a Google Chrome extension that makes the task of developing tests and scraping scripts more efficient.

As a web developer, I often myself trying to figure out what is the best CSS selector for a given element. I've tried many tools, but none of them were good enough. So I decided to create my own.

Rayrun is a Google Chrome extension that helps you to generate CSS selectors for web elements. It is compatible with popular testing tools like Puppeteer, Playwright, Cypress, and Selenium. With Rayrun, you can effortlessly select web elements, regardless of how nested or complex they may be, and swiftly generate precise selectors.

If you are using @playwright/test, Rayrun can also generate Locators (https://playwright.dev/docs/api/class-locator) for you (e.g. `getByLabel('Password')`). You may also use Rayrun to generate XPath selectors (e.g. `//input[@type="submit"]`).

For those familiar with the Playwright [codegen](https://playwright.dev/docs/codegen), the Locator output is similar. The main difference is that Rayrun is a Chrome extension, so you can use it from your browser, which is closer to how I work.

I believe that Rayrun will be a valuable addition to your web development and testing toolkit.

It is my first Chrome Extension so I appologize if you find any glaring mistakes, but please give it a try, share feedback, and I will do my best to address any concerns. I'm here to answer any questions you may have.

Quick note regarding privacy: Rayrun does not collect _any_ data, and it has passed an extended audit by Google Chrome Store team.

Thank you for your time and happy coding!

Hey HN community,

I had quite the day! Earlier today, I shared an article here on HackerNews which to my surprise (and joy!) quickly climbed to the front page - an experience that was entirely new to me.

However, the influx of traffic caught my server off-guard, and the service, regrettably, went down under the weight. I spent the better part of the day scrambling to rectify this, and I've since migrated my hosting to Google Cloud to future-proof against such instances.

Regardless, I feel immensely proud of the article I've written and I believe it would be a shame for it to go unseen just because of some unexpected technical difficulties. I've decided to repost it here, knowing full well it may not achieve the same front-page status. However, my hope is that those who were interested earlier and wanted to give it a read, will now have the chance.

I'm sincerely grateful for your understanding and support. My aim was, and remains, to contribute valuable content to this fantastic community that I've learned so much from.

Here's to fewer technical glitches and more learning experiences in the future! Thank you.

Looks like it is back for some users, but not others. Probably just the time it takes to propagate the DNS. What a bummer! Thank you for helping to troubhelshoot

Its back online and just added Cloudflare in front of it

None. Built it from the ground up!

This has been my weekend project!

This might seem like an odd job board given how incredibly niche it is, however, there is an industry-wide shift happening towards test automation using Playwright and sourcing these jobs at the moment is painstakingly hard.

So I built a job board just for Playwright jobs:

https://ray.run/jobs

All jobs are...

* 100% remote

* using @playwright/test

* manually sourced by me

* link directly to the apply to job form (only Greenhouse and Lever)

It is all manual because there isn't a ton of high-quality jobs worth listing, but I expect this to change over time.

Looking for feedback how to make it better

Done. Thanks!

Hello Hackers! Thrilled to unveil "DevTools," an all-in-one, free utility toolkit. From JSON to YAML conversion, line sorting, to JSON tree visualization - it's got it all!

Why DevTools? Unlike the ad-infested and SEO-optimized fluff out there, DevTools is ad-free, super usable, and online. Designed by a developer, for developers, its nifty features include:

* Practical tools: Only the ones I personally use

* Quick Load: No waiting, just working

* Switching ease: Jump between tools using cmd+k

* Personalization: Save preferences right in the URL

* Transparency: Open-source libraries for each tool, revealed

* Privacy: 100% client-side operation, even works offline

* User-friendly: Double-categorized tools (e.g., function and technology)

* Feedback-ready: Send me your thoughts directly

* Bonus: Related tools handpicked for every tool

Try DevTools and share your feedback.

I would in particular appreciate:

* Suggestions of tools for your use cases

* Feedback on the design and usability (like the eaee of finding tools)

What's next... I want to add a few open AI based tools. This will require sending data to the server, so will need to make that clear in the UI for those tools. A few ideas I've been tinkering with:

* generate regex based on sample data and/or human-language instructions

* help to name a function/variable based on a description

This tool is a learning ground for me to develop websites, experiment with new technologies (like Next.js), and how to collect feedback. Will appreciate all of your feedback!

lol

It gets a boost because it is posted by a YC founder

Oh that is awesome!