op-e2e: Organize e2e system tests in subdirs #11939
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This organizes the op-e2e system tests (the ones using the old
System
/SystemConfig
into sub-dirs within asystem
package.The engine-only system tests went into a new
op-e2e/opgeth
package. This includes fastlz, because the fastlz depend on the same engine setup (at some point we can clean that up).The
System
/SystemConfig
itself are in the newop-e2e/system/e2esys
package.The e2e
InitParallel
/ conditional-test helpers are still in the root of the e2e package.Each of the
system
packages has its ownTestMain
that callsop_e2e.RunMain
, so we can still apply global setting changes where necessary (like in the external-EL mode).I split the mega
system_test.go
into smaller files, categorized into the subdirs based on their function.Helper functions for transactions went into
op-e2e/system/helpers
package. These can move toe2eutils
once we remove theSystemConfig
/System
specific parts about them.Tests
Organizes tests. No new / removed tests.