New issue
Advanced search Search tips

Issue 692926 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Make it easier to run http / wpt tests manually (run server commands should print port numbers)

Project Member Reported by dcheng@chromium.org, Feb 16 2017

Issue description

I've had a number of issues with running http / wtp tests that I think could be improved by adding an info block to the helper scripts.

A few weeks ago, I was trying to debug a wpt test but had no idea how to run it manually. It turns out we have something called run-blink-wptserve, but since I've never used it before, I don't know how http urls map to actual test cases.

Today, I was manually running a http test and trying to figure out why it wasn't failing. It turns out I was using the wrong port #, so all the accesses that should have been cross-origin ended up being same-origin...

1) run-blink-httpd should say what ports it is listening on, and provide an example command line (so people know how the http URL maps to the http/tests directory).
2) run-blink-wptserve should do the same.
 
Cc: qyears...@chromium.org jeffcarp@chromium.org
Labels: Documentation
Status: Available (was: Untriaged)
Sounds good.

Possible next steps:
 1. Add docstrings to the scripts with example usage, and use this docstring content as the description when --help is given.
 2. When starting the server, log the relevant info (ports) etc.

Relevant place in the code: https://cs.chromium.org/chromium/src/third_party/WebKit/Tools/Scripts/webkitpy/layout_tests/servers/cli_wrapper.py
Hm, I just realized after looking at that link that the run-blink-* scripts actually do print port numbers when run with -v.

So the main change to be made here (I think) is to add docstrings and provide example URLs to demonstrate how URLs map to the local directories.
Should this be considered "fixed", or is there some other change that would make this easier?

The run-blink-* scripts do print port numbers if -v is passed, but not by default. Maybe they should print port numbers by default?

Comment 5 by ojan@chromium.org, Feb 27 2017

Cc: -ojan@chromium.org
Labels: -Documentation
Owner: qyears...@chromium.org
Status: Assigned (was: Available)
Summary: Make it easier to run http / wpt tests manually (run server commands should print port numbers) (was: Make it easier to run http / wpt tests manually)
I'm going to answer my question from February, and say that I'd prefer that they log out port numbers by default.
Status: Fixed (was: Assigned)
Looked at it again, and saw that the same code used to start the servers in the run-blink-* commands is used in run-webkit-tests, where we don't necessarily care about port numbers.

Currently status is: Those server commands take --help/-h and --verbose/-v which give you more help, but are still quiet if you don't pass any args.
Project Member

Comment 8 by bugdroid1@chromium.org, Dec 7 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/70b4bd35bef3a4d28feae1419d86908dfb079cdb

commit 70b4bd35bef3a4d28feae1419d86908dfb079cdb
Author: Takeshi Yoshino <tyoshino@chromium.org>
Date: Thu Dec 07 05:24:45 2017

Fix the description argument in run-blink-websocketserver

Bug:  692926 
Change-Id: Iacd04725bfbc2f0beff5bd87b9061d4ba369d6e2
Reviewed-on: https://chromium-review.googlesource.com/807864
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Quinten Yearsley <qyearsley@chromium.org>
Commit-Queue: Takeshi Yoshino <tyoshino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#522348}
[modify] https://crrev.com/70b4bd35bef3a4d28feae1419d86908dfb079cdb/third_party/WebKit/Tools/Scripts/run-blink-websocketserver

Sign in to add a comment