passport keys in passport tests

CHANGELOG.md

@@ -2,6 +2,14 @@
 
 All notable changes to `one-app` will be documented in this file.
 
+## v1.0.2 - 2024-02-25
+
+### What's Changed
+
+* add basic testing workflow by @inmanturbo in https://github.com/envor/one-app/pull/2
+
+**Full Changelog**: https://github.com/envor/one-app/compare/v1.0.1...v1.0.2
+
 ## v1.0.1 - 2024-02-25
 
 ### What's Changed

passport/stubs/tests/Feature/Pest.php

@@ -0,0 +1,68 @@
+<?php
+
+use Envor\Datastore\Datastore;
+use Illuminate\Foundation\Testing\RefreshDatabase;
+use Illuminate\Support\Facades\Artisan;
+use Tests\TestCase;
+
+/*
+|--------------------------------------------------------------------------
+| 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(TestCase::class, RefreshDatabase::class)
+    ->beforeEach(function () {
+
+        Datastore::fake();
+
+        config(['database.platform' => 'testing_platform']);
+        config(['database.default' => 'testing_app']);
+
+        config(['database.connections.sqlite.database' => ':memory:']);
+
+        config(['database.connections.testing_platform' => config('database.connections.sqlite')]);
+
+        config(['database.connections.testing_app' => config('database.connections.sqlite')]);
+
+        Artisan::call('migrate:fresh --database=testing_platform --path=database/migrations/platform');
+
+        Artisan::call('passport:keys', ['--length' => 4096]);
+    })
+    ->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()
+{
+    // ..
+}