Issue 41 in tapestry5-cayenne: Integration tests are flawed

0 views
Skip to first unread message

tapestry...@googlecode.com

unread,
Mar 19, 2012, 1:59:38 PM3/19/12
to tapestry5-caye...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 41 by rfrovarp...@gmail.com: Integration tests are flawed
http://code.google.com/p/tapestry5-cayenne/issues/detail?id=41

Looking at the integration tests for CommitAfter I have discovered that the
page for that test is flawed. By using the Persist annotation on the object
being tested, Tapestry's persistence is actually being tested instead of
Cayenne persistence.

By having setupRender always attempt to load from the DB, you actually test
Cayenne instead of Tapestry.

Attachments:
commitafterpage.patch 1.2 KB

tapestry...@googlecode.com

unread,
Mar 27, 2012, 12:56:40 AM3/27/12
to tapestry5-caye...@googlegroups.com
Updates:
Status: Accepted

Comment #1 on issue 41 by robert.z...@gmail.com: Integration tests are
flawed
http://code.google.com/p/tapestry5-cayenne/issues/detail?id=41

(No comment was entered for this change.)

tapestry...@googlecode.com

unread,
Apr 6, 2012, 1:45:17 AM4/6/12
to tapestry5-caye...@googlegroups.com
Updates:
Status: Fixed

Comment #2 on issue 41 by robert.z...@gmail.com: Integration tests are
flawed
http://code.google.com/p/tapestry5-cayenne/issues/detail?id=41

You actually need to have both @Persist and have the entity loaded at each
render. Technically, you don't /need/ @Persist, but it simplifies the page
logic greatly. In any event, this is now fixed in trunk.

Reply all
Reply to author
Forward
0 new messages