COmanage Developers List

[Benn Oshrin <>]

Let's queue up the CI conversation for our next call and cancel today.

Thanks,

-Benn-

On 6/6/18 8:41 AM, Tom Zeller wrote:
>> Does anybody have anything discussion worthy for Thursday
> 
> Just a mention that I pushed some work on tests.
> 
> On previous calls I had wondered how to lay out the test fixtures. The
> pattern I am following is that 'test' database fixtures (i.e. tables)
> import records from the 'default' database. Since the database setup
> script is run before the tests, the tests assume a newly
> installed/setup instance. Tests which need specific database records
> use custom fixtures stored in a subdirectory, e.g.
> app/Test/Fixture/CoTest. Tests which do not need records imported from
> the 'default' database should use 'empty' fixtures (i.e. empty = no
> records) which are located at app/Test/Fixture/Empty/.
> 
> In passing, I noticed I had to add some fixtures/tables (I think it
> was CoDepartment and CoEmailList) since I last worked on the tests,
> apparently due to some code changes. A CI instance would highlight
> that kind of thing, and I had spent some time setting up Docker
> Compose with the idea of running that on TravisCI. Still looking for
> guidance on CI at some point, especially with GitHub changing hands
> and I think I2 using an enterprise instance.
> 
> Other than that, another nod to Scott for the work on Docker, it has
> been very helpful.
> 
> Tom
>