boojs 0.0.25 → 0.0.26

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 193292e66911d83904cd410eebf9404518ca2758
-  data.tar.gz: 35c56fa2c34e3224de29e58582dd4873c5f3df66
+  metadata.gz: db230cbf699816c58332b402c9323cc8a2247dbd
+  data.tar.gz: 832c8f6043bfc99893297a9d321d1d8ff27337f9
 SHA512:
-  metadata.gz: e7c16d778e4f3392408a2f9605541ddf7b100b2dfce723443c262d6233185f13141f1b9a456b527d01ac666947ca4ac9f0ee3ddb8d56a759488dbd6171b2a7a2
-  data.tar.gz: 4580513131b33187c4a8d2f8e489a353a4b7d89ccb72bb7dc62aba7737c2adbb947c228f75f533ffaf638d1cd77cdd85f5fcb595a791c69a225e5b04013b0b75
+  metadata.gz: ad5ca9aad30b0632ea9aed44e8ed5dfb09bbde16b570af4f08c0adecfe3389ea9b5355ace6a19aeb87061806f838b6a5149d647f81a44bfb2555c2e9ac9d1f48
+  data.tar.gz: ffcedb596fc53da6bf9d3a96e3a685226dd715d08cea17e93912efef2c89517705124328680a245c7e136f545019ceb83c898460628f28053a6314caa5ff69fa

data/README.md

@@ -15,14 +15,14 @@
 **BooJS** was purpose built for our continuous integration infrastructure at [Fittr®](http://www.fittr.com).
 
 # Setup
-```sh
+```js
 #Setup
 gem install boojs
 ```
 
 # Usage
 #### SYNOPSIS
-```sh
+```js
 boojs [-e statement] [-t timeout] [-v file] [file]
 ```
 
@@ -34,27 +34,31 @@ The following options are available:
 
 #### EXAMPLES
 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.
-```sh
+```js
 (sh)>boojs
+console.log("Hello world!");           //Output to $stdout
+console.error("Goodbye cruel world!"); //Output to $stderr
 ```
 
 Same as `boojs` but read the javascript file before reading from stdin.  (i.e. preload a javascript file into your environment)
-```sh
-(sh)>boojs code.js
+```js
+(sh)>boojs jquery.js
+$("body").html("<h1>Hello</h1>");
+console.log($("body").html())
 ```
 
 Execute a javascript statement, and then immediately exit. Exceptions will return 1.
-```sh
+```js
 (sh)>boojs -e "console.log(document);"
 ```
 
 Execute a javascript statement, and then wait 4 seconds before exiting. Exceptions will return 1 and end execution early.
-```sh
+```js
 (sh)>boojs -e "console.log(document);" -t 4
 ```
 
 Verify that a file contains no javascript runtime initialization errors
-```sh
+```js
 (sh)>boojs -v code.js
 (sh)>echo $?
 0
@@ -62,7 +66,7 @@ Verify that a file contains no javascript runtime initialization errors
 
 #### NOTES
   * Calling `booPing()` will immediately return `"pong"` to `stdout`. You may use this to know when boo has started up fully.
-  * `console.error(msg)` will output to stderr.  `console.log(msg) will output to stodut`
+  * `console.error(msg)` will output to `$stderr`.  `console.log(msg)` will output to `$stdout`.
 
 ## Requirements
 
@@ -76,7 +80,7 @@ Verify that a file contains no javascript runtime initialization errors
 
 ---
 
-## FAQ
+## FAQ & Rants
 
 ### Wait, isn't this just NodeJS?
 No, they are for different things. BooJS gives you the full DOM, you can call `document` in BooJS and import arbitrary browser javascript libraries.
@@ -86,13 +90,24 @@ There are a myriad issues with the *PhantomJS repl*; most notably, the *PhantomJ
   * Outputs special format characters even when not attached to a `tty`
   * Does not have well defined behavior which makes it a nightmare to integrate with
   * **Has no support for asynchronous stdin**
+  * Does not output `console.error` to `stderr`
   * Changes what it considers a newline based on the attached terminal (A QT quirk)
   * Is not a unix tool in any sense
 
 I don't think any of this is the `PhantomJS`'s team fault; it's just not their focus or target.
 
-### When should I use boojs?
+### Why would I use BooJS over my browser console?
+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.
+
+### ...Capistrano?
+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.
+
+### Why Ruby?
+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.
 
+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
+
+### When should I use boojs?
 When you need to test javascript code that needs to run in a browser but don't necessarily need to test the UI components.
 
 ### What's Fittr?

data/lib/boojs/version.rb

@@ -1,3 +1,3 @@
 module BooJS
-  VERSION = '0.0.25'
+  VERSION = '0.0.26'
 end

data/lib/boojs.rb

@@ -88,6 +88,7 @@ module BooJS
         phantom.exit(1);
       }
 
+      //@maboiteaspam (https://github.com/ariya/phantomjs/issues/11961)
       console.error = function(msg) {
         system.stderr.writeLine(msg)
       };

data/spec/functions_spec.rb

@@ -37,6 +37,40 @@ RSpec.describe "JS Functions" do
     end
   end
 
+  it "console.log writes to stdout" do
+    @err = StringIO.new
+    @out = StringIO.new
+
+    pipe = Open3.popen3("ruby -Ilib ./bin/boojs") do |i, o, e, t|
+      begin
+        Timeout::timeout(5) do
+          i.puts "console.log('hello world')"
+          loop do
+            res = select [o, e], []
+
+            if res[0].include? e
+              @err.write e.readline
+            end
+
+            if res[0].include? o
+              @out.write o.readline
+            end
+          end
+        end
+      rescue Timeout::Error
+      rescue EOFError
+      ensure
+        begin
+          Process.kill(:KILL, t[:pid])
+        rescue Errno::ESRCH
+        end
+      end
+
+      expect(@out.string.strip).to eq("hello world")
+      expect(@err.string.strip).to eq("")
+    end
+  end
+
   it "booPing writes 'pong' to stdout" do
     @out = StringIO.new
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: boojs
 version: !ruby/object:Gem::Version
-  version: 0.0.25
+  version: 0.0.26
 platform: ruby
 authors:
 - seo