Welcome toBAANGT

Still simple and more powerful ways

As your requirements grow you'd have Testcase and testrun definition separately (e.g. you want to execute the same test cases on different stages of your system landscape (Pre-Quality, Final-Quality, Dev) and not for every heartbeat test you'd want to run through your 1000s of test data. Maybe you'll have a SQL-Query in your Excel based data, which changes data records dynamically or per stage or per version, that you want to test for. Things are not so simple in this stage, but still simple enough for technically versed business department to run high quality tests on all stages by themselves. Even after the point, where you need technicians to integrate baangt with your CD/CI-Pipeline`s buildmanagement tools, the maintenance of data and test sequence can be done without ANY other tools (except Excel or OpenOffice) easily by the people who know best what to test: Your business department

Subclassing for multiply used functionality

The existing classes baangt.TestCase.TestCaseMaster and baangt.TestStep.TestStepMaster can easily be subclassed and enriched with static functionality - even when you use the Excel version of baangt.py. Yes, you'll need to know some basics of powerful Python Language and most probably an IDE.

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 or any other source that 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.

BaangtDB for flexible, powerful enterprise grade test automation

Enter the next stage: baangtDB. baangtDB does much more than just replace Excel as input and sequence source. BaangtDB provides modularization of your test cases. In the above example you'd maintain the Sentry-Popup exactly ONCE for all your test cases, where it applies.

Also if you're in a really large corporate environment, you'll start facing problems with the XLS-Based solution as corporate governance, compliance, regulations and so on will sooner or later make it difficult to use the software in this way. Also even if you use git you experience problems with different versions of the Excel-Sheets - depending on your setup of course.