Skip to content

Add a powerwash e2etest#2311

Open
jmacnak wants to merge 1 commit intogoogle:mainfrom
jmacnak:powerwash
Open

Add a powerwash e2etest#2311
jmacnak wants to merge 1 commit intogoogle:mainfrom
jmacnak:powerwash

Conversation

@jmacnak
Copy link
Copy Markdown
Member

@jmacnak jmacnak commented Mar 26, 2026

Bug: b/360440269
Test: cd e2etests && bazel test cvd/cvd_powerwash_tests/...

@jmacnak jmacnak added the kokoro:run Run e2e tests. label Mar 26, 2026
@GoogleCuttlefishTesterBot GoogleCuttlefishTesterBot removed the kokoro:run Run e2e tests. label Mar 26, 2026
@jmacnak jmacnak force-pushed the powerwash branch 2 times, most recently from 7533fa2 to 3d971fc Compare March 26, 2026 18:45
@jmacnak jmacnak added kokoro:run Run e2e tests. kokoro:force-run Trigger a presubmit build unconditionally. and removed kokoro:run Run e2e tests. labels Mar 27, 2026
@GoogleCuttlefishTesterBot GoogleCuttlefishTesterBot removed the kokoro:force-run Trigger a presubmit build unconditionally. label Mar 27, 2026
@jmacnak jmacnak requested a review from ser-io March 30, 2026 18:10

if err := c.CVDPowerwash(); err != nil {
t.Fatal(err)
}
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it make sense in this test to double check the device was powerwashed?

In the HO e2e test we have the following logic to double check that: https://github.com/google/android-cuttlefish/blob/main/e2etests/orchestration/powerwash_test/main_test.go

Bug: b/360440269
Test: cd e2etests && bazel test cvd/cvd_powerwash_tests/...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants