Side navigation
#13065 closed feature (patchwelcome)
Opened December 16, 2012 05:49PM UTC
Closed December 28, 2012 05:17PM UTC
Should a command-line-driven web server for running Qunit be provided via grunt
| Reported by: | sgharms | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | None |
| Component: | build | Version: | 1.8.3 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
Greetings,
Over in JQueryUI Trac (http://bugs.jqueryui.com/ticket/8904) we've been kicking around a ticket where I asked whether we should provide a CLI-driven startup script for running a minimal, provided web server for the unit tests. It seems like a good idea, but the leadership there recommended the issue be addressed at jQuery core. Thus, I open this issue.
The goal here would be to mirror what I've seen in EmberJS where running a make, er, rake script launches a simple web server sufficient for running the tests. The documentation would then not have to require the prospective contributor to take on the cognitive overhead of finding / installing /configuring a web server - a yak-shave waiting to happen.
I could easily imagine the documentation for jQuery changing to be something like: "To run only the unit tests cd jquery && grunt testserver." This command would do the work of running the server and the equivalent work of grunt watch.
I believe that this would make contributing (with unit tests!) to jQuery easier. I am available for any clarifications should they be required.
Attachments (0)
Change History (2)
Changed December 27, 2012 11:34PM UTC by comment:1
Changed December 28, 2012 05:17PM UTC by comment:2
| component: | unfiled → build |
|---|---|
| priority: | undecided → low |
| resolution: | → patchwelcome |
| status: | new → closed |
Also, all of our ajax tests are written in php so we couldn't just run a node server. Installing node and grunt are not necessarily small tasks for a first-timer either. And oh man, testswarm. Regardless, I'm not sure what to mark this, but I think we'd be willing to look at attempts, so I'll mark patchwelcome.
Most people have a web server running on their dev systems. It's nice to have a self-contained test but it does complicate the setup of jQuery itself. We'd also need to change our testswarm setup so there are other issues to consider.