You can test applications, that are served from the db or consume one of its APIs.
...he final 2.0 release (only minor additions to the query engine were required). If you would like to test them right now, feel free to check out ...
We've been busy since the summer to test and improve everything, so here it is: eXistdb 2.2 final is out! We think this is a major step forward in many areas. To just highlight a few:
...ll as binary documents stored in eXist. To access stored resources, just use a local path, e.g. /db/test/data.json.
...eXist 100% conformant with the XQuery specs: 99.4%! Details can be found on the official W3C XQuery Test Suite pages.
...ce version 1.2.1, eXist also provides a check and export tool, which has the advantage that it will test your db for errors before running the export.
...nd use templateImplement Implement (RFE 1747855)Document 'group by' usageDocument new ant taskAdd test / deep-equalsRedesign webstart / find contextMake more configuration / status info available vi...
...st version of RESTXQ Improved Java Admin Client document viewing and editing Clean up of eXist-db's Test suite Extensive internal refactoring to exploit new Java 8 features lambda expressions where po...
The interface is tested in the junit test suite, but Oracle supplies a vendor independent testsuite as well. Due to licensing limitations this code cannot be included in the eXist-db distribution, but the...
To better understand how the serialization works, I would also suggest to look at the test cases available in file test/src/xquery/json.xml in your eXist directory or SVN.
In order to run the XQuery Test Suite (XQTS), you need to download and install the XQTS data from the W3C web site. To install and run the XQTS, read the following instructions:
I finally ended up with a version that could process the complete XQuery test suite entirely on in-memory documents - achieving the same score (99.4%) as the version which runs on stored documents! Basica...
...nt for your own experiments, though it is not optimized for speed in any way. Note: you may want to test this with eXist trunk, not 1.2.5 (processing in-memory fragments works much faster with trunk).
...in the PersistentLoginModule Disabled auto-deployment of EXPath packages when running tests; faster test suite Switched from MBean to MXBeand for improved JMX client support Further legacy code cleanup...
...423 Offer further build profiles #3386 Update collection.xconf.xsd for eXist 5 #3379 Improve XQuery test naming #3368 Add memory and nr of processors information to startup log. #3335 Group managers ar...
...up Operator (?) for postfix expressions with Maps from XQuery v3.0 Continued clean up of eXist-db's Test Suite Added integration tests to ensure EXPath Package functionality and further support the tri...
...got to the 100%, the harder it became to fix the remaining issues. According to the official XQuery test suite, eXist passes 99.4%, i.e. 14544 out of 14637 tests.
...atest version of RESTXQ Improved Java Admin Client document viewing and editing Clean up of eXist's Test suite Extensive internal refactoring to exploit new Java 8 features Backwards Compatibility issu...
...plit of modules into seperate jars, and moved all modules to lib/extensionsFixed bugs in Fixed XQTS test base-URI-18 regressionFixed construction bug. Fixed: Another NGram bug fix: matches were not ta...
...es in the specification and in the corresponding usecases. These examples are integrated into our test suite.
Question: I am doing a performance test of query operation in eXist，and the result following showed time consumption for query about 10 records increases when the total number of all records stored in da...
We now have all our library functions in place and are ready to use them. For a first test, here's a function which scans the collection hierarchy for resources having a given mime type: