Dear Shuxin Li,
I’m impressed by how you repeatedly manage to discover new bugs in
BaseX. How do you proceed to uncover the errors? Is it a
trial-and-error approach, or are the tests generated automatically? Do
you/does your group plan to write an article that describes your
approach?
All the
Hi Shuxin Li,
It certainly is very impressive work and I am also keen to know more.
I see you have also been working with eXist [1]
I assume it builds on "Query Plan Guidance (QPG), a test case generation
method with the guidance of query plans."? [2]
Best wishes
/Andy
[1]
TEST's about statement is now available in StratML (ISO 17469-1) format at
https://stratml.us/drybridge/index.htm#TEST
Soon it will be discoverable in the query service at
https://search.aboutthem.info/ running on BaseX.
I look forward to learning whether TEST can help identify and resolve
Sorry, Daniel, I overlooked your questions:
> 1. changes that are not saved to disk do not get respected - as opposed to
> other queries
True, this feels confusing. Maybe it would be better to disable the
test icon if the current file has not been saved?
If you prefer to, you can enable the
Dear Shuxin,
I just wanted to take the opportunity to thank you for the bug reports
you've submitted - both here and to the eXist-db project, as Andy noted. I
really like Christian's suggestion to contribute your test cases to the
official W3C test suite. But whichever means you choose, we
Dear Christian, Andy, Owen Ambur and Joe,
Thank you so much for your emails! It's really great to hear from you that
you are interested in our project and appreciate the bug report. It is also
a big encouragement for us.
The tests are automatically generated, and the approach we currently take
6 matches
Mail list logo
