mini_autobot 0.0.2 → 0.0.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 0be74808c6604cb2f503582cc1e3a40319b7bfd3
-  data.tar.gz: a8fe1cdb8886edeb940b2ddde23a45d08d21e9f1
+  metadata.gz: 304864d910ed49b64b576de654ff04d5173e534b
+  data.tar.gz: c7b5881befcfedf13e325e0f3581d7066bd4d04b
 SHA512:
-  metadata.gz: c00a2bfb63e5daf14878cdf70d14eded1ec7a69cc0b655816c433e8a3c92c1ef7bf11ee5b613485659df30194d2713a14e6090bd3313d53130d4202894e288ca
-  data.tar.gz: 5e74bdd9c2d39af94c5d9f678da6f07f1482b324d593ae314125e477fd5001dbc15a203dafbd577618a490802daf767ed35ce58f559be4f47ee0008441354783
+  metadata.gz: 1b57d2ea5b02d55fe7e14e886d32f9ea8cdc7541394bd647297365633171fed553c200ecc101aa67cf81cb91d14d3925d1e46c7d013c3e1f5578249ffbaed208
+  data.tar.gz: f14c61b84e901e72cf1d53cdd3cad30004af1b8ece8d9719efbcf0ecf3f429d081013ac7e902053236517d0fec52bfdd4d987301e743ed5fc9b404aff23a163b

data/README.md

@@ -60,7 +60,9 @@ There are configuration files that are required for it to work properly:
 * Connector profiles, in `config/mini_autobot/connectors/*.yml`, which define WebDriver
   properties, e.g., Firefox, SauceLabs;
 * Environment profiles, in `config/mini_autobot/environments/*.yml`, which define which
-  environment tests are going to run against, e.g., QA, production; and
+  environment tests are going to run against, e.g., QA, production;
+* Test Suite definition, in `config/mini_autobot/test_suite.yml`, which defines tags being used
+  to mark tests for different suites, eg. :non_regression
 
 A typical config file structure looks like this:
 
@@ -86,7 +88,7 @@ A typical config file structure looks like this:
 A Tests Directory Structure file is a regular YAML file, which tells mini_autobot
 where to find tests and which tests to load.
 
-It must be named and placed like this `config/tests.yml` with contents like:
+A typical config file for this looks like:
 
     ---
     tests_dir:
@@ -272,9 +274,14 @@ environment:
     ---
     root: 'http://www.env.host_address.com'
 
+Environment variable as value of `root` is also supported, eg.
+
+    ---
+    root: <%= ENV['DYNAMIC_APP_URL'] %>
+
 #### Test Suite
 
-A typical test suite configuration file `config/test_suite.yml` looks like this:
+A typical test suite configuration file looks like this:
 
     ----
     regression:
@@ -298,9 +305,7 @@ or find the appropriate tag_to_exclude in config/mini_autobot/test_suite.yml
 
 ## Executing Tests
 
-Before you are able to run one or more tests, you'll need to select a connector
-and an environment profile; see the _Configuration_ section below if you want
-to add new profiles.
+See the _Configuration_ section above to have the minimum setup before running tests.
 
 To run test headlessly on default environment(stg), set connector to GhostDriver,
 which is Phantomjs's implementation of webdriver protocal, run:
@@ -319,14 +324,14 @@ Some profiles may contain a section named `overrides`, for example, to support
 multiple browsers in a remote execution environment like SauceLabs. Such
 profiles can be used like this:
 
-    $ bundle exec mini_autobot --connector=saucelabs:linux_ff20 --env=qa
+    $ bundle exec mini_autobot --connector=saucelabs:linux_ff20 --env=rent_qa
 
 which will use the `linux_ff20` override in the `saucelabs` connector profile,
-and run tests against the `qa` environment. Multiple overrides may be specified
+and run tests against the `rent_qa` environment. Multiple overrides may be specified
 one after the other, after the profile name, and always separated by colons,
 for example:
 
-    $ bundle exec mini_autobot -c saucelabs:linux_ff20:qateam:notimeouts -e qa
+    $ bundle exec mini_autobot -c saucelabs:linux_ff20:qateam:notimeouts -e rent_qa
 
 To make a specific connector or environment profile always be the default on
 your machine or shell session, set the `AUTOBOT_CONNECTOR` or `AUTOBOT_ENV`
@@ -334,9 +339,9 @@ environment variables respectively. For example, you can add the following to
 your shell profile (`.bash_profile` for bash or `.zlogin` for zsh):
 
     export AUTOBOT_CONNECTOR=firefox
-    export AUTOBOT_ENV=qa
+    export AUTOBOT_ENV=rent_qa
 
-Refer to the _Configuration_ section below for advanced use cases, and refer
+Refer to the _Configuration_ section above for advanced use cases, and refer
 to `mini_autobot -h` for a complete list of command line options.
 
 
@@ -405,9 +410,6 @@ For example, to run all tests in sign_in.rb,
 
     $ bundle exec mini_autobot -t class_signin
 
-
-Read Rakefile for how to run test with default settings through rake tasks
-
 #### Debug output
 
 It's not good style to clutter your code with puts messages. Instead, use the
@@ -445,11 +447,11 @@ To see a list of options and reporters from gem TAPOUT,
 
 To use our custom reporter, FancyTapReporter,
 
-    $ bundle exec mini_autobot --tapy | tapout -r ./lib/tapout/custom_reporters/fancy_tap_reporter.rb fancytap
+    $ bundle exec mini_autobot --tapy | tapout -r $(bundle show mini_autobot)/lib/tapout/custom_reporters/fancy_tap_reporter.rb fancytap
 
 To make it presentable to jenkins or other webpage, supress color/highlight codes,
 
-    $ bundle exec mini_autobot --tapy | tapout --no-color -r ./lib/tapout/custom_reporters/fancy_tap_reporter.rb fancytap
+    $ bundle exec mini_autobot --tapy | tapout --no-color -r $(bundle show mini_autobot)/lib/tapout/custom_reporters/fancy_tap_reporter.rb fancytap
 
 
 ## Test Cases
@@ -494,7 +496,6 @@ Similarly, test cases should be provided as an attribute on the class:
 See {Running a Subset of Tests} for information on the `tags` option.
 
 
-
 ## Page Objects
 
 Parts of a page should be added under `MiniAutobot::PageObjects::Components`, and
@@ -536,6 +537,13 @@ its best to return the current page as an object, ie:
       end
 Overlays are technically not new pages, and should be differentiated from actual pages.
 
+#### Widgets
+
+A widget represents a portion (an element) of a page that is repeated
+or reproduced multiple times, either on the same page, or across multiple
+page objects or page modules.
+
+
 ## Best Practice
 
 * Always use local variables, unless _absolutely_ necessary, then use instance

data/lib/mini_autobot/connector.rb

@@ -55,13 +55,12 @@ module MiniAutobot
 
       return unless MiniAutobot.settings.auto_finalize?
 
-      Thread.new do
-        while connector = self.finalization_queue.pop
-          begin
-            connector.finalize!
-          rescue => e
-            MiniAutobot.logger.error("Could not finalize Connector(##{connector.object_id}): #{e.message}")
-          end
+      while self.finalization_queue.size > 0
+        connector = self.finalization_queue.pop
+        begin
+          connector.finalize!
+        rescue => e
+          MiniAutobot.logger.error("Could not finalize Connector(##{connector.object_id}): #{e.message}")
         end
       end
     end

data/lib/mini_autobot/version.rb

@@ -1,3 +1,3 @@
 module MiniAutobot
-  VERSION = '0.0.2'
+  VERSION = '0.0.3'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: mini_autobot
 version: !ruby/object:Gem::Version
-  version: 0.0.2
+  version: 0.0.3
 platform: ruby
 authors:
 - Ripta Pasay
@@ -10,7 +10,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-08-12 00:00:00.000000000 Z
+date: 2015-08-18 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport