catchpoint/WebPageTest.api-nodejs

Where can I see the history of submitted jobs?

NickTulett opened this issue · 7 comments

The agent machine the tests ran on just shows the history of jobs submitted manually. Where are the node.js tests?

Is it because testlog.php needs auth and a gmail address in the cookie to show private jobs?

I've forced $includePrivate in line 24 to true in my private instance for now.

Sorry, yes. Usually private tests are only visible to the "user" that submitted it (where user is tracked by login or by browser cookies). That means for private API tests you usually won't see them in the history and need to keep track of the ID's.

If you want them to show up in the log for everyone you can just run them as public tests (don't pass the private=1 flag).

It doesn't seem to make any difference as to whether the private flag is present or not, or whether it's set to true or false or 1 or 0, I can only see my results if I set $includePrivate to true in testlog.php and select "all users" in the UI.

Something else must be going on because it should behave just like the
public instance where you can see all of the non-private tests as long as
you check the "see tests from all users" box:
http://www.webpagetest.org/testlog.php?days=1&all=on

When you run non-private tests do you get the shorter test ID's? i.e.

Private: 140929_TT_b68c77cf6fc77a1efe639e3a08bc3aab
Public: 140929_5D_12Y0

On Mon, Sep 29, 2014 at 10:13 AM, Nick Tulett notifications@github.com
wrote:

It doesn't seem to make any difference as to whether the private flag is
present or not, or whether it's set to true or false or 1 or 0, I can only
see my results if I $includePrivate to true in testlog.php and select "all
users" in the UI.


Reply to this email directly or view it on GitHub
#24 (comment)
.

No, I always get long IDs whether I run tests through the UI or node.js if the test has a script.

If it's a simple URL test, I get the short ID.

Any chance the tests are for pages behind basic auth? That's the only thing I can think of that would implicitly set the private flag on a test.

Ah yes, there we are. I had login and password values in the settings even though I explicitly set them in the script. Now I get the short URLs and can see the results in the history without hacks.

Learn something new every day...