INTRODUCING TEBER

All the open-sourced frameworks for automation works fine on standalone mode, but difficulties faced while integrating with 3rd party repo's for our customized usage gives us a solid reason to have a common framework on top of the collective open-sourced stacks. 

For Instance, If we need to consider running the automation suite in the Linux machine or in the Docker container, we need to have the capability to change the mode of run via CLI. This might be simple, but we need a little bit of configuration from our end every time.

When we integrate with many modules, some of the methods may be common in both the modules, which in turn raises the headache of calling them individually with their proper namespace. For example, Capybara and Allure have attach_file method as common, when someone includes both in a project they could find this clash.

To have integration with Continuous Integration (CI) we are in need to find an alternative with respect to reporting. To mitigate the issues faced while integrating with third-party reporting services which gives better illustration on reports, It's better to have a tightly coupled framework in this front.

To have a common coding standard and practices among all the people in a team, project, or organization so that resource reallocation will have a smooth transition.