Readme next try

README.md

@@ -12,28 +12,38 @@ pip install baangt
 Clone the repository: ``GIT CLONE https://gogs.earthsquad.global/baangt``
 
 Then fire up your favorite virtual environment, e.g. 
-`CONDA create baangt`, activate it, e.g. `CONDA activate baangt` and install the necessary requirements: `pip install -r requirements.txt` and you're good to go.
+`CONDA create baangt`, activate it, e.g. `CONDA activate baangt` and install the necessary requirements: 
+`pip install -r requirements.txt` and you're good to go.
 #Usage:
-``baangt`` can be used for API, oData V2/V4, Browser (Chrome, Firefox, Safari, IE and more) Testing based on a common data layer. As complex as this sounds, as easy is it to start with, give it a try!
+``baangt`` can be used for API, oData V2/V4, Browser (Chrome, Firefox, Safari, IE and more) Testing based on a common 
+data layer. As complex as this sounds, as easy is it to start with, give it a try!
 ##Preparation:
 You need at least a data- and a sequence definition file (example: `DropsSimple.xlsx` in the root folder of `baangt`).
 ##Run the Testcase
-``Python baangt.py --run="DropsSimple.xlsx"`` will execute the testcases defined in the file (login to drops-app, recycle a product)
+``Python baangt.py --run="DropsSimple.xlsx"`` will execute the testcases defined in the file (login to drops-app, recycle 
+a product)
 ##Receive the results
-You'll find the output file in the folder `1testoutput` as XLSX with a summary of duration, successful vs. non-successful testcases and a second tab with details for each looped testcase.
+You'll find the output file in the folder `1testoutput` as XLSX with a summary of duration, successful vs. non-successful 
+testcases and a second tab with details for each looped testcase.
 ##Awesome, but not enough?
-You're deeply impressed by the simplicity of the solution, but want MORE? We've got you covered. The second example shows the same outcome with much greater flexibility. For the second execution you'll use DropsTestRunDefinition.xlsx-File. You can see, that there are more Tabs than in the first example, for instance can you specify which datafile and tabname(s) to use for execution of a testrun, which lines from the datafile to skip/run, which browser to use and much more.
+You're deeply impressed by the simplicity of the solution, but want MORE? We've got you covered. The second example shows 
+the same outcome with much greater flexibility. For the second execution you'll use DropsTestRunDefinition.xlsx-File. 
+You can see there are more Tabs than in the first example, for instance can you specify which datafile and 
+tabname(s) to use for execution of a testrun, which lines from the datafile to skip/run, which browser to use and much more.
 Calling ``baangt.py`` is still same simple:
 `Python baangt.py --run="DropsTestRunDefinition"`. Again you'll find an excel sheet in the folder `1Testoutput`.
 ##Nice(r), but how about a real life example?
 You're right. Nobody can test his application with 5 datafields and 1 business process. 
 
-Real life regression tests often span multiple applications (thus we use TestCaseSequence), many business processes (the testcases) and each of them in countless variations (datafile with usage of TestStepSequences). 
+Real life regression tests often span multiple applications (thus we use TestCaseSequence), many business processes 
+(the testcases) and each of them in countless variations (datafile with usage of TestStepSequences). 
 No matter, how complex the application under test is, the start is always a Testrun definition. 
 
-Btw. try `python baangt.py` without parameters to start the UI. It should run on Mac, Windows and all major Linux-Distributions with X11 
+Btw. try `python baangt.py` without parameters to start the UI. It should run on Mac, Windows and all major 
+Linux-Distributions with X11 
 ##Still want more? Create your own TestStepClass:
-Every once in a while the TestStep-Definition via XLSX or the database will not be enough for your use-case. You can easily subclass whatever you need and still use the rest of the framework.
+Every once in a while the TestStep-Definition via XLSX or the database will not be enough for your use-case. You can 
+easily subclass whatever you need and still use the rest of the framework.
 ```
 from baangt.TestStep import TestStepMaster
 
@@ -45,9 +55,13 @@ class myTestStep(TestStepMaster):
 
 ```
 
-That's it. All the rest is taken care of by baangt. You'll also receive a nice export file showing timing information for your TestCase.
+That's it. All the rest is taken care of by baangt. You'll also receive a nice export file showing timing information 
+for your TestCase.
 
-You can subclass any other functionality, that doesn't fully fit your needs (IBAN-Generation, Browser-Handling, Timing) and also create your own Assertion-classes (for instance if you need to receive data from a Host-System or RFC/SOAP-Connection, which is not natively supported by ``baangt.py``). Of course you'd only re-implement methods, that you need to enrich and consume everything else from the framework.
+You can subclass any other functionality, that doesn't fully fit your needs (IBAN-Generation, Browser-Handling, Timing) 
+and also create your own Assertion-classes (for instance if you need to receive data from a Host-System or 
+RFC/SOAP-Connection, which is not natively supported by ``baangt.py``). Of course you'd only re-implement methods, 
+that you need to enrich and consume everything else from the framework.
 
 ##Browser related knowledge
 ###Setting, which browser to start