chore: prep systemstest (#24514)

systemtests/CHANGELOG.md

@@ -36,7 +36,7 @@ Ref: https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.j
 
 ## [Unreleased]
 
-## [v1.1.0] -  2025-04-24
+## [v1.2.0] -  2025-04-24
 
 * SDK v0.53.x support.
 

systemtests/README.md

@@ -29,7 +29,7 @@ Therefore, we focus on the **critical path** and do not cover every condition.
 
 ## How to use
 
-Read the [getting_started.md](../systemtests/getting_started.md) guide to get started.
+Read the [GETTING_STARTED](../systemtests/GETTING_STARTED.md) guide to get started.
 
 ### Execute a single test
 

tests/systemtests/README.md

@@ -2,7 +2,7 @@
 
 Go black box tests that setup and interact with a local blockchain. The system test [framework](../../systemtests) 
 works with the compiled binary of the chain artifact only.
-To get up to speed, checkout the [getting started guide](../../systemtests/getting_started.md).
+To get up to speed, checkout the [getting started guide](../../systemtests/GETTING_STARTED.md).
 
 Beside the Go tests and testdata files, this directory can contain the following directories:  
 
@@ -33,16 +33,3 @@ cp ./build/simd ./tests/systemtests/binaries/
 ```shell
 go test -v -mod=readonly -failfast -tags='system_test' --run TestStakeUnstake    ./... --verbose
 ```
-
-### Working with macOS
-
-Most tests should function seamlessly. However, the file [upgrade_test.go](upgrade_test.go) includes a **build annotation** for Linux only.
-
-For the system upgrade test, an older version of the binary is utilized to perform a chain upgrade. This artifact is retrieved from a Docker container built for Linux.
-
-To circumvent this limitation locally:
-1. Checkout and build the older version of the artifact from a specific tag for your OS.
-2. Place the built artifact into the `binaries` folder.
-3. Ensure that the filename, including the version, is correct.
-
-With the cached artifact in place, the test will use this file instead of attempting to pull it from Docker.