• last updated 54 mins ago
Constraints: committers
Constraints: files
Constraints: dates
Test the behavior when the multirow contains values in the form "\d+\.": this shows a bug caused by the value retrieval going through an expr, which will "normalize" the value to "\d+\.0"

Implement a test making sure ::xo::dc "loop code-executing" api is not subject to the "out of pools" bug

Remove hack and prefer to document limitation in the automated test

  1. … 1 more file in changeset.
Test that appending to an existing multirow from the db works as expected: when the columns defined via query and extend are the same, this should succeed

Don't collide with multirows created by other tests

Test ::xo::dc multirow further

- break and continue behavior in the code block (this will expose a bug)

- appending to an existing multirow

Extend automated tests to cover new ::xo::dc multirow api

Remove test of undocumented format to specify prepared statement

Basic test of xo::dc foreach when using prepared statements

This api currently supports the flag, but will ignore it

Extend test for prepared statements containing strings with colon characters, exposing that the latest commit won't address all cases

Make test more consistent

Introduce a test exposing that when a statement is prepared on SQL containing colons, this sould fail because they would be interpreted as variables

Basic test of the prepared statements feature on ::xo::dc api

update list of checked procs

improve documentation and streamline code

  1. … 2 more files in changeset.
improve listing of test coverage

  1. … 6 more files in changeset.
improve listing of test coverage

  1. … 8 more files in changeset.
make listing of tested procs more complete

  1. … 11 more files in changeset.
extend test coverage

  1. … 1 more file in changeset.
Add a quick run of the basic CRUD operations on ORM to avoid issues when e.g. no particular object member is explicitly supplied

Modifying IP really comes from the item and not from the revision (as normally comes from the automatically generated view ${table_name}i which says so)

Do not return empty context_ids for the test, make sure value will have to change

Test behavior before and after a full fetch, make sure that the chosen context_id is not the previous one

Be stricter in CrItem tests as well

Be stricter and treat known suboptimal behaviors in ORM interface as test failures

Fix xotcl-core cr-items test: modifying IP comes in fact from the cr_item's acs_object (it is also on the revision, but on the items seems to take into account e.g. proxying)

Improve boolean existance checks

Add a couple more tests about properties of revisions

Add basic CrItem tests

file xotcl-test-procs.tcl was initially added on branch oacs-5-10.