Files
Chronos/tests/Chronos.Core.Tests/Metadata/MetadataTestHelpers.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

26 lines
1.0 KiB
C#

using Chronos.Core.Metadata;
using Chronos.Testing;
namespace Chronos.Core.Tests.Metadata;
internal static class MetadataTestHelpers
{
public static FrameMetadata Read(byte[] data, string? fileName = null, DateTime? modified = null) =>
MetadataReader.Read(new MemoryStream(data, writable: false), fileName, modified);
/// <summary>The reader's safety net turns parser defects into "Parser fault" warnings; tests require none.</summary>
public static void AssertNoFault(FrameMetadata m)
{
foreach (var w in m.Warnings)
{
if (w.StartsWith("Parser fault", StringComparison.Ordinal)) Assert.Fail(w);
}
}
public static void AssertPreviews(FrameMetadata m, params (int Width, int Height, PreviewKind Kind)[] expected)
{
Assert.SequenceEqual(expected, m.Previews.Select(p => (p.Width, p.Height, p.Kind)), "previews");
foreach (var p in m.Previews) Assert.True(p.Offset > 0 && p.Length > 0, $"preview at {p.Offset} length {p.Length}");
}
}