boojs 0.0.27 → 0.0.28
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +1 -11
- data/lib/boojs/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 4a232579090bb10937efd0fdf9e55a2cded42a95
|
|
4
|
+
data.tar.gz: f1d678f045eab0c0f0a2b50b4384cea5294c7a5d
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: e71c8cc1d66fd9780784101a59200a76c629c060c4f620feb47a663c44f5dba4f4e7458c94c889bacf022b891445b21e667a5334be7dd0b4613c11130e09c34b
|
|
7
|
+
data.tar.gz: e7fa516576a4a53d16a478af901ce8a335501830288c9d618cedac78414ef6ebf915c3c7d538f13deacb18817580714d00a64439260b2cb46154abc5b2225b30
|
data/README.md
CHANGED
|
@@ -31,6 +31,7 @@ The following options are available:
|
|
|
31
31
|
* `-e` - Pass a javascript statement to execute after the file (if a file is provided) and then immediately terminate unless `-t` is set.
|
|
32
32
|
* `-t` - Close the program after N seconds have passed, if an exception is raised before this, terminate immediately
|
|
33
33
|
* `-v` - Verify that a file contains no javascript syntax errors. Returns 0 if there are no errors.
|
|
34
|
+
* `-p` - Outputs the PID of the spawned sibling process as the first line of stdout. Used for unit specs.
|
|
34
35
|
|
|
35
36
|
#### EXAMPLES
|
|
36
37
|
Open a javascript pipe that reads from stdin, writes via console.log to stdout, prints exceptions via stderr, and exits with a return code of 1 if there are errors.
|
|
@@ -96,17 +97,6 @@ There are a myriad issues with the *PhantomJS repl*; most notably, the *PhantomJ
|
|
|
96
97
|
|
|
97
98
|
I don't think any of this is the `PhantomJS`'s team fault; it's just not their focus or target.
|
|
98
99
|
|
|
99
|
-
### Why would I use BooJS over my browser console?
|
|
100
|
-
You wouldn't, if you preferred that. *BooJS* was designed for continuous integration environments and has evolved into fun for shell scripting (i.e. `netcatesque`) and even dynamic website page analysis. Some users also prefer CLI over GUI.
|
|
101
|
-
|
|
102
|
-
### ...Capistrano?
|
|
103
|
-
Capistrano is great for integration tests for behaviors; many users prefer to use both `BooJS` for the javascript layer and then `Capistrano` for behavioral testing, especially with frameworks like `cucumber`. `BooJS` is faster to boot and and more determinant than `Capistrano` while `Capistrano` is able to verify behavior across browsers and visuals. They go well togeather.
|
|
104
|
-
|
|
105
|
-
### Why Ruby?
|
|
106
|
-
Ruby has many shortcomings; Nonetheless, ruby is an excellent language for writing tools in. Ruby has a culture of testing, a mature gem database that contains many *js* parsers, increadible syntax that includes N-embeddable strings within strings without ugly escape sequences, and good support for `POSIX` interfaces.
|
|
107
|
-
|
|
108
|
-
Did you know that *WebKit* uses *Ruby* to pre-compile it's **Javascript** bytecode interpreter *LLInt*? https://trac.webkit.org/browser/releases/Apple/Safari%206.0.2/JavaScriptCore/offlineasm
|
|
109
|
-
|
|
110
100
|
### When should I use boojs?
|
|
111
101
|
When you need to test javascript code that needs to run in a browser but don't necessarily need to test the UI components.
|
|
112
102
|
|
data/lib/boojs/version.rb
CHANGED