Adds Pest tests. Starts GH Action.

tests/Feature/DockerCommandsTest.php

@@ -0,0 +1,32 @@
+<?php
+
+use Tests\Support\Output;
+
+it('starts a docker container correctly', function () {
+
+    $coolifyNamePrefix = 'coolify_test_';
+    $format = '{"ID":"{{ .ID }}", "Image": "{{ .Image }}", "Names":"{{ .Names }}"}';
+    $areThereCoolifyTestContainers = "docker ps --filter=\"name={$coolifyNamePrefix}*\" --format '{$format}' ";
+
+    // Generate a known name
+    $containerName = 'coolify_test_' . now()->format('Ymd_his');
+    $host = 'testing-host';
+
+    // Assert there's no containers start with coolify_test_*
+    $processResult = coolifyProcess($areThereCoolifyTestContainers, $host);
+    $containers = Output::containerList($processResult->output());
+    expect($containers)->toBeEmpty();
+
+    // start a container nginx -d --name = $containerName
+    $processResult = coolifyProcess("docker run -d --name {$containerName} nginx", $host);
+    expect($processResult->successful())->toBeTrue();
+
+    // docker ps name = $container
+    $processResult = coolifyProcess($areThereCoolifyTestContainers, $host);
+    $containers = Output::containerList($processResult->output());
+    expect($containers->where('Names', $containerName)->count())->toBe(1);
+
+    // Stop testing containers
+    $processResult = coolifyProcess("docker stop $(docker ps --filter='name={$coolifyNamePrefix}*' -q)", $host);
+    expect($processResult->successful())->toBeTrue();
+});

tests/Feature/ExampleTest.php

@@ -1,19 +0,0 @@
-<?php
-
-namespace Tests\Feature;
-
-// use Illuminate\Foundation\Testing\RefreshDatabase;
-use Tests\TestCase;
-
-class ExampleTest extends TestCase
-{
-    /**
-     * A basic test example.
-     */
-    public function test_the_application_returns_a_successful_response(): void
-    {
-        $response = $this->get('/');
-
-        $response->assertStatus(200);
-    }
-}

tests/Pest.php

@@ -0,0 +1,48 @@
+<?php
+
+/*
+|--------------------------------------------------------------------------
+| Test Case
+|--------------------------------------------------------------------------
+|
+| The closure you provide to your test functions is always bound to a specific PHPUnit test
+| case class. By default, that class is "PHPUnit\Framework\TestCase". Of course, you may
+| need to change it using the "uses()" function to bind a different classes or traits.
+|
+*/
+
+uses(
+    Tests\TestCase::class,
+    // Illuminate\Foundation\Testing\RefreshDatabase::class,
+)->in('Feature');
+
+/*
+|--------------------------------------------------------------------------
+| Expectations
+|--------------------------------------------------------------------------
+|
+| When you're writing tests, you often need to check that values meet certain conditions. The
+| "expect()" function gives you access to a set of "expectations" methods that you can use
+| to assert different things. Of course, you may extend the Expectation API at any time.
+|
+*/
+
+expect()->extend('toBeOne', function () {
+    return $this->toBe(1);
+});
+
+/*
+|--------------------------------------------------------------------------
+| Functions
+|--------------------------------------------------------------------------
+|
+| While Pest is very powerful out-of-the-box, you may have some testing code specific to your
+| project that you don't want to repeat in every file. Here you can also expose helpers as
+| global functions to help you to reduce the number of lines of code in your test files.
+|
+*/
+
+function something()
+{
+    // ..
+}

tests/Support/Output.php

@@ -0,0 +1,17 @@
+<?php
+
+namespace Tests\Support;
+
+use Illuminate\Support\Collection;
+
+class Output
+{
+    public static function containerList($rawOutput): Collection
+    {
+        $outputLines = explode(PHP_EOL, $rawOutput);
+
+        return collect($outputLines)
+            ->reject(fn($line) => empty($line))
+            ->map(fn($outputLine) => json_decode($outputLine, flags: JSON_THROW_ON_ERROR));
+    }
+}