My application for sponsorship of #jqwik 2 by @PrototypeFund has been rejected (again).
I've decided to no longer apply for public funding. Given the high # of applicants and me being outside the intended target group (young, diverse teams), the chances of making it are just too low. It's not only about the application effort but also about the need to block the funding period from other endeavours until notification.
Thus, I consider two different paths for the future of #jqwik: ...
1/n
Release 1.9.2 of #jqwik is now available on Maven Central: https://jqwik.net/release-notes.html#192
I just started another #jqwik 2 API discussion: What is the most useful package naming scheme?
https://github.com/jqwik-team/jqwik2-api-discussion/issues/5
Version 1.9.1 of #jqwik has just been released: https://jqwik.net/release-notes.html#191
@jlink Good opportunity to point to the ongoing #jqwik 2 API design discussions:
1. Arbitraries, Generators and Transformations (https://github.com/jqwik-team/jqwik2-api-discussion/issues/1)
2. Fundamental Arbitrary Types (https://github.com/jqwik-team/jqwik2-api-discussion/issues/2)
3. Combining Arbitraries (https://github.com/jqwik-team/jqwik2-api-discussion/issues/3)
4. Specifying and Validating Arbitraries (https://github.com/jqwik-team/jqwik2-api-discussion/issues/4)
I just published a blog entry about the next generation of Property-based Testing and why #jqwik needs a version 2:
https://blog.johanneslink.net/2024/09/13/next-gen-pbt/
@marcphilipp @odrotbohm It’s not easy :-/ What I did with my #jqwik survey last year: I searched for relevant repos on GH and then opened an issue there that pointed to the survey. „Relevant“ in your case: a) test engines b) Jupiter extensions. In my case, most opened issues resulted in survey answers.
Currently, five different API suggestions for #jqwik 2 can be discussed on Github:
1. Arbitraries, Generators and Transformations (https://github.com/jqwik-team/jqwik2-api-discussion/issues/1)
2. Fundamental Arbitrary Types (https://github.com/jqwik-team/jqwik2-api-discussion/issues/2)
3. Combining Arbitraries (https://github.com/jqwik-team/jqwik2-api-discussion/issues/3)
4. Specifying and Validating Arbitraries (https://github.com/jqwik-team/jqwik2-api-discussion/issues/4)
5. Packages naming scheme (https://github.com/jqwik-team/jqwik2-api-discussion/issues/5)
IMO item 4 is the most important because it's a completely new way to use Jqwik from any testing framework.
The #jqwik team has its first sponsor: https://github.com/sponsors/jqwik-team/dashboard/your_sponsors
Many thanks, @goerge
One more API discussion issue for #jqwik 2. This time about how to specify and validate properties programmatically.
https://github.com/jqwik-team/jqwik2-api-discussion/issues/4
Probably the last one before summer break.
On the Future of #jqwik
I've just received a rejection from @sovtechfund
about funding jqwik maintenance and/or the development of version 2.
This raises a fundamental question about the future of jqwik.
My current employer pays for 2 hours per week, which I use to maintain it.
2 hrs are just enough for bug fixes, dependency upgrades and minor improvements.
It's definitely not enough for the planned version 2 rewrite.
1/x
Should the #jqwik website block access from AI bots as described in https://darkvisitors.com/docs/robots-txt ?