I'm doing a research on software testing (integrated testing, debugging and maintenance environments) and I found this Travis CI, but my English is not very good and I did not find articles in Portuguese. Basically, what is Travis CI for? And how can I make use of it?
What is Travis CI?
8
asked by anonymous 12.04.2017 / 00:57
2 answers
8
CI stands for Continuous integration , ie this refers to a series of tests that you can write to ensure your code and related work as expected through unit testing.
Some useful links:
Travis-CI is a tool that you integrate with your online repository (in this case, I believe, only Github) so that every time you upload an update, Travis-CI itself will test in the environments you want / configure.
For example, assuming I wrote a script for PHP and set up phpunit (unit test for PHP), then I set the .travis.yml that should be in the same repository like this:
language: php
php:
- 5.6
- 7.0
- 7.1
Of course you should also put in the repository the tests you wrote (depending on the technology you use)
This will make Travis-CI test only my script only in PHP versions 5.6, 7.0 and 7.1, an example Laravel : link
See that Travis-CI does everything without you having to install anything and you can point to your page or file .md (like README.md ) an image to check the current state:
<img src="https://travis-ci.org/laravel/framework.svg"alt="Build Status">
Just if it's green this is Ok, other colors may be minor glitches or the test has not passed.
Travis-CI does not only support PHP, in fact it supports many languages or technologies and with this different types of tests (of course you are writing):
12.04.2017 / 01:39
5
It's a seamless integration tool. This is a methodology that preaches that everything that is being done about development must be integrated immediately, usually several times a day. So you have the centralized project where all developers are putting their modifications where the system is tested and built completely showing if something is going wrong and identifying problems as soon as they appear and not later when it can be more complicated.
When I speak in tests I speak of a set of quality checks and not just unit tests.
In some cases the implementation itself is simulated to make sure everything is ok.
Some people question how useful this is. There are those who demonstrate that there are difficulties in operating this way.
Obviously, in small teams the utility becomes much smaller, but it is still possible to benefit from the automation of the complete quality assurance process.
Travis CI takes care of all of this (if properly configured for each task, it does not guess anything, gives a job all the time leaving everything in order, but can save a lot of work as well) and it communicates with several other tools that support the development of team software. He alone does nothing.
It controls the flow of the source repository, the build, the various unit, integration, load, performance, static and dynamic tests, creates documentation, simulates or even prepares the bug , eventually even opens tickets .
12.04.2017 / 04:43