alasql / alasql-sqllogictest

sqllogictest for AlaSQL

SQLlogictest for AlaSQL

Testing SQL compabillity for AlaSQL on the 5,047,257 tests from http://www.sqlite.org/sqllogictest

See the most recent result

Why?

AlaSQL src should incorporate test cases from sqllogictest [1] to identify areas where AlaSQL does not comply with the expectations to traditional SQL statements.

The goal (for now) is not to pass all the tests, but to help us describe (in the documentation) what AlaSQL does not support - and by that identify areas to improve for the library.

[1] https://github.com/grahn/sqllogictest/tree/master/test

The format of the tests are desribed here: http://www.sqlite.org/sqllogictest/doc/trunk/about.wiki

How?

Install dependencies `npm install and run all the tests with:

npm test

The result will output to results/output.md

To make sure you are testing the most recent version of AlaSQL please run the following:

npm install alasql

Please see the config section of the run files to run tests on local version instead of npm version.

What?

The output of run.js is the output of each test file followed by the total score. (so you can keep track of the overall % of passed tests while its running)

There are 5,047,257 tests in the full test suite. Many of the tests will trigger the same kind of error - this is why the output will only print the same error the first time it comes forward. To have more examples, there is a (low) probability it print errors again even if it has been printed before. You can also choose to print all errors. Please see the config section in the run.js file.

Please note that the current version of the script ONLY TESTS IF THE SQL CAN COMPILE - not if the returned values are correct.

Output

The output from run.js is structured the following way:

• Date and time for the run
• Information about how many test files will used
• [notice if this does not represent all test files in the test folder]
• Listing path to each testfile to be used
• For each test file
  • Name of the test file that is about to run
  • If errors occure the original SQL triggering the error is printed followed by the javascript error description.
  • Summary of error rate in this test file and time consumption
  • Summary of error rate for all test file
• Note stating: "ALL TESTS COMPLETED"

The output from a single testfile could look like this

11/32 ./test/index/delete/1000/slt_good_0.test

Mimic sqlite

★ Ran 11,924 tests as sqlite

• 100% was OK

sqlite 11924 OK: ./test/index/delete/1000/slt_good_0.test

It makes sense, as no errors were found. But it can also look like this:

6/32 ./test/index/commute/100/slt_good_0.test

Mimic sqlite

☓ Ran 10,122 tests as sqlite

• 20 failed
• 99% was OK

making less sense as an error was found but was not printed. Because there are about 5 million tests in the full testset the same errors will be found many times. To limit noise an error only gets printed first time its seen. Settings for printing errors can be found in the config section of run.js

Supported

• Verify that the parser parses all the tests

• Floating point values are rendered as if by printf("%.3f").

• NULL values are rendered as "NULL". Empty strings are rendered as "(empty)". Within non-empty strings, all control characters and unprintable characters are rendered as "@".

• Implement verification of returned valued with sortorder set

ToDo

• Change the compatibility flags in AlaSQL according to whats mimicked

• implement:

The argument is also optional. If included, sqllogictest stores a hash of the results of this query under the given label. If the label is reused, then sqllogictest verifies that the results are the same. This can be used to verify that two or more queries in the same test script that are logically equivalent always generate the same output.

Not ToDo

• Implement mocha testframework (testresults does not get printed before all are done - so it fills the memory)