Project

General

Profile

Bug #1660

Tests fail due to web-server not starting

Added by Luke Murphey about 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Luke Murphey
Category:
Unit Tests
Target version:
4.0.2
Start date:
12/19/2016
Due date:
% Done:

100%

History

#1 Updated by Luke Murphey about 8 years ago

Observations:

  • The logs indicate that the server was started but the function to start the web-server is being called more than once

21:06:06.960 [exec] Waiting for web-server to start ... Done
21:06:08.964 [exec] Waiting for web-server to start ...Traceback (most recent call last):

It could be that setUpClass() is getting called more than once

#2 Updated by Luke Murphey about 8 years ago

Made setUpClass() reentrant. It still seems that these are being called out of order. I think that the test suite is calling setUpClass() before the entire suite is running. This means that the mere existence of one test cases blocks all of the other ones. Here are the tests that use the test web-server:

  • TestWebInput
  • TestRawContent
  • TestCustomSeparator
  • TestBrowserRenderingFirefox (TestBrowserRendering)
  • TestBrowserRenderingIntegrated (TestBrowserRendering)

#3 Updated by Luke Murphey about 8 years ago

Since the web-server is using a daemon thread, I think I can have the server setup globally for the test class and let the daemon thread stop itself at the end.

#4 Updated by Luke Murphey about 8 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF