Files
Chronos/tests/Chronos.Tools.Tests/PackInstallerCommandTests.cs
T
Alby96andClaude Opus 5.5 5f27a86406
CI / Build and test (pull_request) Failing after 2m3s
CI / PostgreSQL 16 integration (pull_request) Skipped
CI / PostgreSQL 17 integration (pull_request) Skipped
CI / Docker image (pull_request) Skipped
CI / Windows tests and installer (pull_request) Skipped
CI / YAML check (pull_request) Successful in 4s
refactor!: rename Titano to Chronos and move CI and releases to Gitea
The owner renamed the product and moved the repository to the self-hosted
Gitea (https://gitea.encke-hake.ts.net/BalboSoft/Chronos) for more control,
and asked for Actions and a first automatic release with the server package
and the Windows exe (docs/requests/2026-10-23-chronos-gitea.md).

- Chronos everywhere: a byte-exact rename of contents and paths, then a
  per-language review of the forms the old name's ending had dictated.
- Gitea instead of GitHub: the update check, licence, issue and support
  links read ChronosReleasesUrl; the update check takes the highest stable
  version, offers a pre-release build its final release and reports a
  repository it cannot see as a failed check. EULA, security policy and
  Gitea issue forms live at the repository root.
- Gitea Actions for the Linux act_runner (.gitea/workflows): CI, release,
  nightly image and performance gates in the .NET SDK container with git
  checkout. The release cross-compiles the Windows programs, checks their
  icon, version and DPI manifest, packs installers and zips, publishes the
  Gitea release and pushes the server image (REGISTRY_TOKEN). Windows-only
  tests run in an opt-in job on a Windows runner (WINDOWS_RUNNER).
- New Chronos.Tools commands: zip, gitea-release, postgres-ci (replaces the
  docker-exec script, which Gitea's service containers do not allow) and
  pe-check.

BREAKING CHANGE: programs, settings, data folders, file types, environment
variables and the Docker image use the new name; nothing is migrated from
Titano, which never had a release.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 11:34:48 +02:00

45 lines
1.9 KiB
C#

using Chronos.Core.Packaging;
using Chronos.Testing;
using Chronos.Tools.Commands;
namespace Chronos.Tools.Tests;
/// <summary>pack-installer writes the components, shortcuts and file types setup installs (BRIEF §18).</summary>
public sealed class PackInstallerCommandTests(TestContext context)
{
[Test]
public async Task TheServerInstallsOnlyForAllUsersAndChronosOwnsTheProjectFileType()
{
var root = context.CreateTempDirectory("pack");
var stub = Path.Combine(root, "Chronos.Setup.exe");
var bytes = new byte[4096];
new Random(5).NextBytes(bytes);
"MZ"u8.CopyTo(bytes);
await File.WriteAllBytesAsync(stub, bytes);
var app = Program(root, "app", "Chronos.exe");
var server = Program(root, "server", "Chronos.Server.exe");
var output = Path.Combine(root, "out", "Chronos-Setup.exe");
Assert.Equal(0, await new PackInstallerCommand().RunAsync(
["--setup", stub, "--product", "Chronos", "--version", "1.2.3", "--component", "Chronos=" + app, "--component", "Server=" + server, "--out", output]));
using var reader = PayloadReader.Open(output);
var manifest = reader.Manifest;
Assert.False(manifest.FindComponent("Chronos")!.AllUsersOnly);
var serverComponent = manifest.FindComponent("Server")!;
Assert.True(serverComponent.AllUsersOnly);
Assert.False(serverComponent.DefaultSelected);
var association = Assert.Contains(manifest.Associations, a => a.Extension == ".chronos");
Assert.Equal("Chronos.Project", association.ProgId);
Assert.Equal("Chronos.exe", association.Target);
Assert.Equal("Chronos", association.Component);
}
private static string Program(string root, string folder, string name)
{
var dir = Directory.CreateDirectory(Path.Combine(root, folder)).FullName;
File.WriteAllText(Path.Combine(dir, name), "MZ " + name);
return dir;
}
}