💯 I don’t think anyone who has been here for a while is taking shots from the cheap seats. Users who are actually using these apps and are sharing their wishes and frustrations are the best feedback any dev is going to get. They’re fools if they don’t listen.

Until QA becomes a higher priority, Nostr won't see sustained growth. It might not be sexy, but it's the true path forward.

@OpenSats , @Gigi , @ODELL , has anyone applied to build a test suite for nostr? Is there any reason to think this is an unreasonable task, @fiatjaf , @utxo the webmaster 🧑‍💻 ?

Absolutely. Feature creep has been the death of countless promising tech startups. I get that not everyone agrees that growth is the right KPI, but as the adage goes, you're either growing or you're dying.

@elsat had an idea of NostrCI. Not sure if that went anywhere.

I'd bet on him.

Ehhhh, I don't see how a generic test suite would catch the types of issues Derek is pointing out, but perhaps I am regarded . Usually they have to be app specific and extremely well planned out to catch crashy type scenarios

We are looking for an investor who can lend 75,000 US dollars to our holding. We are going to establish a furniture manufacturing facility, but we are short of 75,000 US dollars to complete our budget. Therefore, we would like to borrow 75,000 US dollars from you. In today's industry, the furniture business ensures fast sales and also provides great profit opportunities. We will open a furniture production facility in Baku, Azerbaijan, with the 75,000 dollars you will give. You will lend 75,000 US dollars to our holding. When the date 22.12.2025 comes, I will return your money as 750,000 US dollars. You will lend 75,000 US dollars to our holding company. When 22.12.2025 comes, I will give you your money back as 750,000 US dollars. You will have made 10 times profit in 9 months When 22.12.2025 comes, you will get your money back as 750,000 US dollars The link below is the link to our website. For detailed information, open the link to our website below and review the articles on our website in detail. To learn how you can lend 75,000 US dollars to our holding and to get detailed information about our project, please review the articles on our website in the link below. The link below is the link of our website. Detailed information is available on our website. For detailed information, check out our website at the link below. Our website link: https://adenholding313.wixsite.com/adenholding/investment-info

@elsat has wanted something like that for years and I always tell him it's an impossible task.

I think he just means a common test suite

I’m definitely looking at it as a Profit machine :P

Yes. I'm not a dev, so I'm reaching, maybe, but is it not reasonable to build test suites for the most commonly used libraries?

@AU9913 is working on a nostrCI proof of concept. More details to follow

This is actually a good observation... GM 😘

Not impossible, fairly simple POC. Once the poc is done it's at matter of getting funding to grind out use cases. The matrix of use cases is also fairly trivial to generate. Likely the hardest part will be the mobile testing. Probably the idea would be to run these on @Arjen's cicd DVM so anyone can trigger and pay the invoice.

We can use @sandwich 's validation tool, running them on decentralized (GitHub actions) workflow runners using gitworkshop.

These are up to date, with some known inaccuracies (and in production use) Schema:

GitHub

nostr-watch/libraries/schemata at next · sandwichfarm/nostr-watch

A NIP-66 nostr client for browsing nostr relays. Contribute to sandwichfarm/nostr-watch development by creating an account on GitHub.

TS/JS Validators:

GitHub

nostr-watch/libraries/schemata-js-ajv at next · sandwichfarm/nostr-watch

A NIP-66 nostr client for browsing nostr relays. Contribute to sandwichfarm/nostr-watch development by creating an account on GitHub.

I'm confused what I'm looking at. This isn't something for testing, it's for validating data as it comes into the relay, correct

It's for validating data, in general. A huge percentage of interoperability issues between clients relates to missing tags or missing data within tags.

Validation and QA are different things tho right? Or am I thinking about this incorrectly

Not sure, I was just primarily responding to @Arjen since he linked to the nostrability repo that hasn't been updated in almost 6 months. Wanted to clarify. If Client A puiblishes a NIP-22 events without a root event tag, then Client B (and perhaps event Client A) won't be able to find it. Schemas can catch this error either in production or in a CI/CD pipeline. It can also detect these issues by fuzz testing events. I would personally consider that QA, but maybe not?

Validation can be one task in the process of QA. It's not the whole thing but def important

@Arjen what are you getting at? I'm unsure how you're saying to use this for qa. Like I get it for apps to use, but I don't understand what you're saying about using this when testing clients.

But why? The whole point of QA is to use broken events and see how the clients react. Also, it's to use working events and see how they react. Once the test data is generated you won't really have to validate? Sorry I think I'm missing something