CI CD - TestlumFramework/Testlum GitHub Wiki

CI/CD

In simple words, CI / CD (Continuous Integration, Continuous Delivery - continuous integration and delivery) is a technology for automating testing and delivering new modules of a project under development to interested parties (developers, analysts, quality engineers, end users, etc.).

Testlum easily integrates with software development and testing tools that use the CI / CD method. Namely with tools such as:

  1. VCS (Git, Bitbucket, etc.)
    • The environment allows you to manage project repositories, document the functionality and results of improvements and tests, as well as track errors, and work with the CI / CD pipeline.
  2. Docker
    • Automatic project deployment system. It supports containerization and allows you to pack the project along with all the environment and dependencies into a container.
  3. Jenkins (or any CI/CD tool)
    • Customize CI/CD processes for specific product development requirements.
AWS

All together it will allow us to ensure the promptness of the output of new product functionality (working with customer requests). As a rule, it is a matter of days or weeks. At the same time, with the classical approach to developing a client’s software, this could take a year. In addition, the development team receives a pool of code alternatives, which optimizes the cost of resources for solving the problem (by automating the initial testing of the functionality). Parallel testing of the functional blocks of the future system enhances the quality of the product. Bottlenecks and critical moments are captured and processed early in the cycle.

With the help of Testlum and CI / CD development, the Product Owner takes full control of the entire phase of development and testing of his product. This allows the testing team to improve software quality, run continuous regression testing, and monitor software quality in real-time with the ability to run parallel tests. Moreover, it will allow developers to monitor the cleanliness of the written code by running their branches on builds. Thus, we conclude that it becomes even easier to develop the perfect software.

Logs in Jenkins have become more pleasant to read by customizing logs in Testlum

AWS
⚠️ **GitHub.com Fallback** ⚠️