Repository navigation
test: skip blocktank order and cjit creation tests - #1699
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Regtest APKDownload bitkit-dev-debug universal APK (expires in 30 days). |
[Low impact] This PR appears safe to merge. SummarySkips
ovitrif explicitly intends to disable these two tests because staging no longer supports creation. The skipped creation coverage is the stated scope, not an unintended loss of coverage. Reviews (1) · Last reviewed commit: "test: skip blocktank order and cjit crea..." · Reviewed by Greptile |
talosmachina
left a comment
There was a problem hiding this comment.
No findings. Puts @Ignore on the two BlocktankTest cases that create a Blocktank order or a CJIT entry, now that staging refuses those writes. Reviewed ac49b32, light tier. Reasoned from the code and CI, not built here.
What I checked, and 3 candidates I ruled out
Read in full: BlocktankTest.kt
Call sites traced: createCjit, createOrder and estimateFee across app/src/androidTest and app/src/test
CI: build, lint, detekt and the APK job are green. build-local and Greptile were still pending. BlocktankTest only runs in UI Tests (push to master or dispatch), so no PR check exercises this file.
Ruled out
- Another instrumented test still creates orders:
createCjitis called only intestCreateCjitEntry. ThecreateOrderhits inTransferViewModelTest.ktare against a mockedblocktankRepo, so they never reach staging. testOrderEstimateis also a write and fails the same way: it posts to the estimate endpoint, not to/channels. AgainstEnv.blocktankApiUrlfor regtest (https://api.stag0.blocktank.to/blocktank/api/v2) just now,GET /infoandPOST /channels/estimate-fee-fullreturned 200 andPOST /channelsreturned 404, so the two cases left running are the ones staging still serves.- Kotlin warnings break compilation (
allWarningsAsErrors):@Ignoreleaves the method bodies compiled and every import in use, so nothing becomes unused.
Merge confidence: 4/5, no findings, but the only workflow that runs BlocktankTest is the UI Tests dispatch the body links, and it is not a check on this PR.
Reviewer model: claude-opus-5-5
Reasoning effort: Not exposed (the review runner does not report a reasoning setting)
|
UI Tests on this branch: https://github.com/synonymdev/bitkit-android/actions/runs/40356197449
The run still fails on five tests that make no Blocktank order. Each one also fails on master before the read-only switch:
|
Twin: synonymdev/bitkit-ios#1130
Companion: synonymdev/bitkit-e2e-tests#285
Refs: synonymdev/blocktank-lsp-http#168
Description
POST /channelsandPOST /cjitreturn 404.BlocktankTest.testCreateCjitEntryBlocktankTest.testOrderstestGetInfo,testOrderEstimate) and the regtest deposit/mine tests keep running.Out of Scope
Design
N/A — no UI changes.
Preview
N/A — no user-visible changes.
QA Notes
Journeys
N/A — no user-visible behaviour change.
Manual Tests
N/A
Automated Checks
BlocktankTest.kt— order and CJIT creation cases ignoredEvidence
BlocktankTestruns only in theUI Testsworkflow (push to master or dispatch); a dispatch on this branch is linked in a comment below.Gaps
None.
Models used
Claude Opus 5.5(reasoning:low)Claude Opus 5.5(reasoning:low)