Ophir LOJKINE
95f228f383
* simplify SQL test files - Simplified SQL test files by removing unnecessary components and restructuring queries to focus on expected vs actual results. - Updated the request handling in `run_sql_test` to differentiate between JSON and HTML responses based on test file content. - Enhanced error handling and assertions for both JSON and HTML responses to improve test reliability and clarity. - Removed redundant code and improved readability in the test execution flow. * move more tests to the new expected/actual format * migrate more tests to the expected/actual format - Changed references in various test files to point to the new `simple.sql` instead of the outdated `it_works_simple.sql`. - Removed several obsolete SQL test files that are no longer needed, streamlining the test suite. - Updated assertions and request paths in the test cases to reflect the new structure and improve clarity. * Enhance error handling in SQL tests and update SQL syntax - Added a new function `format_error` to improve error reporting in SQL test assertions, capturing detailed error descriptions and backtraces. - Updated SQL syntax in `sqrt.sql` to use `INT` instead of `integer` for consistency with SQL standards. * sqrt test
18 lines
855 B
Markdown
18 lines
855 B
Markdown
The sql files in this folder are all tested automatically. They are organized in
|
|
two subdirectories:
|
|
|
|
## `component_rendering/`
|
|
|
|
Files that depend on SQLPage's HTML rendering (components, shells, redirects,
|
|
etc.). Every file that does not start with `error_` must render a page that
|
|
contains the text "It works !" and no occurrence of the word "error" (case
|
|
insensitive). `error_` files should return a page containing the word "error"
|
|
and the rest of the file name. Files may include `nosqlite`, `nomssql`,
|
|
`nopostgres` or `nomysql` in their name to skip incompatible backends.
|
|
|
|
## `data/`
|
|
|
|
Files that only validate data-processing functions should live here. They must
|
|
return rows with an `actual` column plus either `expected` (exact match) or
|
|
`expected_contains` (substring match). Tests in this directory are fetched as
|
|
JSON and validated row by row. |