Activity OpenACS/openacs-4/packages/xotcl-core/tcl/test/xotcl-test-procs.tcl

Tree
Accordion

Stats

Commits this week: 0

Total Committers:	2
Last Commit:	26 Apr
Commits this week:	0
Total Lines of Code (LoC):	0
Net change in LoC this week:	0

Commit Activity

last updated 5 hours ago

Constraints

Constraints: committers

Committer:

Log Comment:

Constraints: files

File Extension:

File Name:

Constraints: dates

Start Date:

End Date:

Tuesday 23 Apr 2019

7:00 pm

antoniop

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)

- -8
- +8
./xotcl-test-procs.tcl
- History
- Source
- Diff
./xotcl-test-procs.tcl

4:26 pm

antoniop

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

- -2
- +2
./xotcl-test-procs.tcl
- History
- Source
- Diff
./xotcl-test-procs.tcl

Wednesday 17 Apr 2019

4:54 pm

antoniop

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

- -0
- +18
./xotcl-test-procs.tcl
- History
- Source
- Diff
./xotcl-test-procs.tcl

2:38 pm

antoniop

Be stricter in CrItem tests as well

- -43
- +31
./xotcl-test-procs.tcl
- History
- Source
- Diff
./xotcl-test-procs.tcl

2:22 pm

antoniop

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

- -29
- +40
./xotcl-test-procs.tcl
- History
- Source
- Diff
./xotcl-test-procs.tcl

Monday 15 Apr 2019

2:04 pm

antoniop

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)