Duckpan tester

[yegg]

Since duckpan has dependencies on internal code, it can break without us realizing it (like it did the past day or so). We could use an automated testing script that we can run periodically to check if it is in a functional state or not. I imagine this would run independently of duckpan, spin up duckpan server and then run some tests against it.

Part of the issue here, however, is that the error could be in JavaScript and that is hard to detect without something like Selenium. So maybe we do it that way, or maybe we treat those separately and for now we just run a script that tests more basic functioning, which could get most of the cases easily.

cc @nilnilnil @moollaza

[moollaza]

@yegg one thing to keep in mind is that when Duckpan requests a resource that doesn't exists on DDG (i.e. HTML, JS, CSS) it doesn't get a 404 (which is why it didn't failover to use the local, cached copy of the file) but instead it gets a copy of the SERP where the query is the filename. I suppose this is the best way of making sure we actually got the file requested, rather than HTML DuckPAN can't use.

[javathunderman]

@moollaza ping, is there any update on this?

[moollaza]

@javathunderman no, this isn't really a priority right now, we have different plans for the direction of duckpan and how IA's should be tested :)