9bdcbe0447
Major integrations and fixes: - Added BACKBEAT SDK integration for P2P operation timing - Implemented beat-aware status tracking for distributed operations - Added Docker secrets support for secure license management - Resolved KACHING license validation via HTTPS/TLS - Updated docker-compose configuration for clean stack deployment - Disabled rollback policies to prevent deployment failures - Added license credential storage (CHORUS-DEV-MULTI-001) Technical improvements: - BACKBEAT P2P operation tracking with phase management - Enhanced configuration system with file-based secrets - Improved error handling for license validation - Clean separation of KACHING and CHORUS deployment stacks 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
30 lines
856 B
Go
30 lines
856 B
Go
// Package require implements the same assertions as the `assert` package but
|
|
// stops test execution when a test fails.
|
|
//
|
|
// # Example Usage
|
|
//
|
|
// The following is a complete example using require in a standard test function:
|
|
//
|
|
// import (
|
|
// "testing"
|
|
// "github.com/stretchr/testify/require"
|
|
// )
|
|
//
|
|
// func TestSomething(t *testing.T) {
|
|
//
|
|
// var a string = "Hello"
|
|
// var b string = "Hello"
|
|
//
|
|
// require.Equal(t, a, b, "The two words should be the same.")
|
|
//
|
|
// }
|
|
//
|
|
// # Assertions
|
|
//
|
|
// The `require` package have same global functions as in the `assert` package,
|
|
// but instead of returning a boolean result they call `t.FailNow()`.
|
|
//
|
|
// Every assertion function also takes an optional string message as the final argument,
|
|
// allowing custom error messages to be appended to the message the assertion method outputs.
|
|
package require
|