Show HN: PatchGirl – QA for Web Developers | Hacker News Reader

Show HN: PatchGirl – QA for Web Developers

patchgirl.io

28 pointsmatsutsu46 comments

I don't fully understand what this is.

This seems to be a tool to allow me to semi-automate repetitive tasks that access a REST API; is that correct? Can I download it and fill it in with my own endpoints, etc?

Kind of :-) The idea behind PatchGirl is to allow developers to combine REST and SQL requests to populate your database to a desired state. The goal is to make "database seeding" and "API testing" reproducible and ease manual testing :-)

All PatchGirl's features are enabled by running a little proxy (called patchgirl-runner) on your computer which you can find here https://github.com/patchgirl/patchgirl/releases/tag/v3.0.0

Feedbacks are much appreciated!!

One comment based on a discussion I was having yesterday on this subject, I’d be careful of the term seeding. I think of seed data as data required for the app to function properly. For example, I seed my application database with a system user account or other system specific data.

I’d contrast this with test data which is used to provide a consistent data set for reproducible actions (usually unit or integration tests).

Sorry if that’s a pedantic nuance

I'd say the definition is whatever definition the team you work in uses. For example for me at work, seeding = automatic database setup for a test system with example data

  > I'd say the definition is whatever definition
  > the team you work in uses.

No, the definition of industry terms is the way they would be understood by other people in the industry. Seeding is understood to be critical data such as area code lists and timezone information.

  > For example for me at work, seeding = automatic
  > database setup for a test system with example data

You're not wrong. Seeding _is_ automatic database setup, just not only for test systems.

>No, the definition of industry terms is the way they would be understood by other people in the industry. Seeding is understood to be critical data such as area code lists and timezone information.

That's kind of the point. Ask three different people in the industry, get three slightly different definitions, unless they work in the same team.

> Uncaught TypeError: Cannot read property 'childNodes' of undefined at _VirtualDom_addDomNodesHelp (app.js:3616) at _VirtualDom_addDomNodesHelp (app.js:3624) at _VirtualDom_addDomNodesHelp (app.js:3624) at _VirtualDom_addDomNodes (app.js:3540) at _VirtualDom_applyPatches (app.js:3647) at app.js:3937 at updateIfNeeded (app.js:3972)

Scenarii is very pretentious. I know you are going with the Italian plural, but it's not an English word. It's really out of place on the landing page.

I don't get the gender backlash here, personification has been a thing for a long time and there doesn't seem to be any malfeasance (intended or otherwise) here. It's not lewd, doesn't play to stereotypes, etc.

To me, a basic litmus test is whether you could easily swap the gender without reworking anything. If you can't, it's probably offensive, if you can it's practically gender neutral (naming aside). It's not a catch all, obviously, as it's no replacement for awareness of history, culture, stereotypes etc.

It's easy enough to maintain a rebranded mirror synced to upstream. Instead people seem to want to take offense just for the sake of virtue signaling.

In the end we should all be using the genderless term, "dude" . Im a dude, he's a dude, she's a dude, we are all dudes.

Dude, dude is gendered. Female version is dudette.

Idk about that

Get with the slang, old dude/dudette.

> doesn't play to stereotypes

The stereotype that QA is 'women's work' is harming the industry.

Can you point me to any examples of that stereotype? Historical employment figures, long form discussions, etc? I've genuinely never heard of that one, and considering the dominant solution in this space is Postman an alternative, female gendered solution could be argued as inclusive.

I've been in web development for over a decade and have never heard of this. All of the QA teams that I've worked with in the past have never showed any preference for one gender over the other.

QA and BAs skew slightly female but not really all that much. It's just a stark contrast to devs that skew pretty overwhelmingly male.

>Instead people seem to want to take offense just for the sake of virtue signaling.

Are you taking offense to people taking offense for the sake of virtue signaling?

There's nothing wrong with gender.

Reply on news.ycombinator.com