Hi Chris, Hi Steven,
> Have you measured it, eg by replacing the message with a constant? By
> what percentage does it speed up a successful test run?
How far is significant for `one` test? Please exchange the zip method
against `itertools.product` and some message creation with concatenation
(us
On Sat, Aug 26, 2017 at 08:25:41PM +0200, francismb wrote:
> Hi all,
> while using `unittest` I see the pattern of creating an error message
> with the test context for the case that some `assert...` methods fails
> (to get a good error message). On the lines:
[...]
> The `msg` is just used in case
On Sun, Aug 27, 2017 at 4:25 AM, francismb wrote:
> Hi all,
> while using `unittest` I see the pattern of creating an error message
> with the test context for the case that some `assert...` methods fails
> (to get a good error message). On the lines:
>
> class Test...(unittest.TestCase):
>
> lo
Hi all,
while using `unittest` I see the pattern of creating an error message
with the test context for the case that some `assert...` methods fails
(to get a good error message). On the lines:
class Test...(unittest.TestCase):
longMessage = True
def test_(self):
...
for a, b, c ...
