Deploy to gh-pages branch: base commit ea4c9fb851f00de72a97d8282283e1d0f84a6193

Travis CI · Travis CI · commit d04d827b419c · 2020-03-17T21:01:04.000Z
diff --git a/utPLSQL/develop/about/authors.md b/utPLSQL/develop/about/authors.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.11.3357--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.11.3367--develop-blue.svg)
 
 ### utPLSQL v3 Major Contributors 
 
diff --git a/utPLSQL/develop/about/license.md b/utPLSQL/develop/about/license.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.11.3357--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.11.3367--develop-blue.svg)
 
 # Version Information
 
diff --git a/utPLSQL/develop/about/project-details.md b/utPLSQL/develop/about/project-details.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.11.3357--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.11.3367--develop-blue.svg)
 
 # utPLSQL Project Details
 
diff --git a/utPLSQL/develop/about/support.md b/utPLSQL/develop/about/support.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.11.3357--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.11.3367--develop-blue.svg)
 
 # How to get support
 
diff --git a/utPLSQL/develop/index.md b/utPLSQL/develop/index.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.11.3357--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.11.3367--develop-blue.svg)
 
 # Introduction to utPLSQL
 
@@ -57,7 +57,7 @@ Amongst many benefits they provide ability to:
 * use many reporting formats simultaneously and save reports to files (publish)
 * map your project source files and test files into database objects 
 
-Just download the [latest client](https://github.com/utPLSQL/utPLSQL-cli/releases/latest), download Oracle jdbc driver you are good to go.
+Download the [latest client](https://github.com/utPLSQL/utPLSQL-cli/releases/latest) and you are good to go.
 See [project readme](https://github.com/utPLSQL/utPLSQL-cli/blob/develop/README.md) for details.  
 
 # Coverage
diff --git a/utPLSQL/develop/userguide/advanced_data_comparison.md b/utPLSQL/develop/userguide/advanced_data_comparison.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.11.3357--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.11.3367--develop-blue.svg)
 
 # Advanced data comparison
 
diff --git a/utPLSQL/develop/userguide/annotations.md b/utPLSQL/develop/userguide/annotations.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.11.3357--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.11.3367--develop-blue.svg)
 
 # Annotations
 
@@ -2064,9 +2064,15 @@ When processing the test suite `test_employee_pkg` defined in [Example of annota
 
 ## sys_context
 
-It is possible to access information about currently running suite, test and befire/after procedure form within PLSQL procedure using SYS_CONTEXT.
-
+It is possible to access information about currently running suite.
 The information is available by calling `sys_context( 'UT3_INFO', attribute )`.
+It can be accessed from any procecure invoked as part of utPLSQL test execution.
+
+**Note:**
+> Context name is derived from schema name where utPLSQL is installed.
+> The context name in below examples represents the default install schema -> `UT3`
+> If you install utPLSQL into another schema the context name will be different.
+> For example if utPLSQL is installed into `HR` schema, the context name will be `HR_INFO`
 
 Following attributes are populated:
 - Always:
diff --git a/utPLSQL/develop/userguide/best-practices.md b/utPLSQL/develop/userguide/best-practices.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.11.3357--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.11.3367--develop-blue.svg)
 
 # Best Practices
 
diff --git a/utPLSQL/develop/userguide/coverage.md b/utPLSQL/develop/userguide/coverage.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.11.3357--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.11.3367--develop-blue.svg)
 
 # Coverage
 utPLSQL comes with a built-in coverage reporting engine. The code coverage reporting is based on the DBMS_PROFILER package provided with Oracle database.
@@ -243,7 +243,7 @@ By default, utPLSQL will convert file paths into database objects using the foll
 > This is done to simplify the syntax of regular expressions. Regular expression will always use '/' as a directory separator on a file path regardless of whether you're on a Windows or Unix system.    
 
 **Note**
-> Below examples assume that you have downloaded latest version of [utPLSQL-cli](https://github.com/utPLSQL/utPLSQL-cli/releases), extracted it into your projects root directory (my_project) and placed ojdbc8.jar and orai18n.jar files in utPLSQL-cli\lib directory.
+> Below examples assume that you have downloaded latest version of [utPLSQL-cli](https://github.com/utPLSQL/utPLSQL-cli/releases) and extracted it into your projects root directory (my_project).
 > The examples assume that you run the utPLSQL-cli from `my_project` directory.    
 
 Windows:
diff --git a/utPLSQL/develop/userguide/exception-reporting.md b/utPLSQL/develop/userguide/exception-reporting.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.11.3357--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.11.3367--develop-blue.svg)
 
 # Exception handling and reporting
 
diff --git a/utPLSQL/develop/userguide/expectations.md b/utPLSQL/develop/userguide/expectations.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.11.3357--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.11.3367--develop-blue.svg)
 
 # Expectation concepts 
 Validation of the code under test (the tested logic of procedure/function etc.) is performed by comparing the actual data against the expected data.
diff --git a/utPLSQL/develop/userguide/getting-started.md b/utPLSQL/develop/userguide/getting-started.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.11.3357--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.11.3367--develop-blue.svg)
 
 # Getting started with TDD and utPLSQL
 
diff --git a/utPLSQL/develop/userguide/install.md b/utPLSQL/develop/userguide/install.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.11.3357--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.11.3367--develop-blue.svg)
 
 # Downloading latest version of utPLSQL
 
@@ -225,7 +225,7 @@ To grant utPLSQL to an individual user, execute scripts `source/create_user_gran
 Example invocation:
 ```bash
 cd source
-sqlplus ut3_user/ut3_password@database @create_user_grants.sql ut3 hr
+sqlplus ut3_owner_schema/ut3_password@database @create_user_grants.sql ut3 hr
 sqlplus user/user_password@database @create_user_synonyms.sql ut3 hr
 ```
 
diff --git a/utPLSQL/develop/userguide/querying_suites.md b/utPLSQL/develop/userguide/querying_suites.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.11.3357--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.11.3367--develop-blue.svg)
 
 # Qyerying for test suites
 
diff --git a/utPLSQL/develop/userguide/reporters.md b/utPLSQL/develop/userguide/reporters.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.11.3357--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.11.3367--develop-blue.svg)
 
 utPLSQL provides the following reporting formats.
 
diff --git a/utPLSQL/develop/userguide/running-unit-tests.md b/utPLSQL/develop/userguide/running-unit-tests.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.11.3357--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.11.3367--develop-blue.svg)
 
 # Running tests
 
@@ -31,7 +31,6 @@ curl -Lk "${DOWNLOAD_URL}" -o utplsql-cli.zip
 unzip -q utplsql-cli.zip
 ```
 
-Keep in mind that you will need to download/provide Oracle JDBC driver separately, as it is not part of utPLSQL-cli due to licensing restrictions.
 
 # ut.run
 
diff --git a/utPLSQL/develop/userguide/upgrade.md b/utPLSQL/develop/userguide/upgrade.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.11.3357--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.11.3367--develop-blue.svg)
 
 # Upgrading from version 2
 
diff --git a/utPLSQL/index.md b/utPLSQL/index.md
@@ -5,7 +5,7 @@ layout: default
 # Documentation
 
  - [Latest v3.1.10 documentation](latest/) - Created 23 Feb 2020 - 04:38:12 PM
- - [Latest development version](develop/) - Created 14 Mar 2020 - 06:33:26 PM
+ - [Latest development version](develop/) - Created 17 Mar 2020 - 09:01:04 PM
 
 ## Documentation release history
 

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-![version](https://img.shields.io/badge/version-v3.1.11.3357--develop-blue.svg)`
	`1`	`+![version](https://img.shields.io/badge/version-v3.1.11.3367--develop-blue.svg)`
`2`	`2`
`3`	`3`	`### utPLSQL v3 Major Contributors`
`4`	`4`