Issue 18 in livecoding: MODE_UPDATE and unit tests

1 view
Skip to first unread message

livec...@googlecode.com

unread,
Feb 22, 2010, 10:25:08 PM2/22/10
to py-livecod...@googlegroups.com
Status: Accepted
Owner: richard.m.tew
Labels: Type-Defect Priority-Medium Component-Logic Usability

New issue 18 by richard.m.tew: MODE_UPDATE and unit tests
http://code.google.com/p/livecoding/issues/detail?id=18

Are unit tests copied over in MODE_UPDATE? If so, they should not be.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

livec...@googlecode.com

unread,
Feb 22, 2010, 10:56:17 PM2/22/10
to py-livecod...@googlegroups.com

Comment #1 on issue 18 by richard.m.tew: MODE_UPDATE and unit tests
http://code.google.com/p/livecoding/issues/detail?id=18

For now, I have disabled the copying of subclasses of unittest.TestCase,
but it is
desirable to look at what else may be copied over before closing this issue.

Reply all
Reply to author
Forward
0 new messages