Documentation ¶
Index ¶
- func ConsensusNotStarted() tests.SpecTest
- func DuplicateDutyFinished() tests.SpecTest
- func DuplicateDutyNotFinished() tests.SpecTest
- func Finished() tests.SpecTest
- func FirstHeight() tests.SpecTest
- func NotDecided() tests.SpecTest
- func PostDecided() tests.SpecTest
- func PostFutureDecided() tests.SpecTest
- func PostInvalidDecided() tests.SpecTest
- func PostWrongDecided() tests.SpecTest
- func Valid() tests.SpecTest
- type MultiStartNewRunnerDutySpecTest
- type StartNewRunnerDutySpecTest
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
func ConsensusNotStarted ¶
ConsensusNotStarted tests starting duty after prev already started but for some duties' consensus didn't start because pre-consensus didnt get quorum (different duties will enable starting a new duty)
func DuplicateDutyFinished ¶ added in v0.3.1
DuplicateDutyFinished is a test that runs the following scenario:
- Runner is assigned a duty
- Runner finishes the duty
- Runner is assigned the same duty again
func DuplicateDutyNotFinished ¶ added in v0.3.1
DuplicateDutyNotFinished is a test that runs the following scenario: - Runner is assigned a duty - Runner doesn't finish the duty - Runner is assigned the same duty again
func FirstHeight ¶ added in v0.3.4
FirstHeight tests a valid start duty at slot 0
func NotDecided ¶
NotDecided tests starting duty before finished or decided
func PostDecided ¶
PostDecided tests a valid start duty before finished and after decided of another duty. Duties that have a preconsensus phase won't update the `currentRunningInstance`.
func PostFutureDecided ¶ added in v0.3.0
PostFutureDecided tests starting duty after a future decided This can happen if we receive a future decided message from the network and we are behind.
func PostInvalidDecided ¶
PostInvalidDecided tests starting a new duty after prev was decided with an invalid decided value
func PostWrongDecided ¶
PostWrongDecided tests starting a new duty after prev was decided wrongly (future decided) This can happen if we receive a future decided message from the network.
Types ¶
type MultiStartNewRunnerDutySpecTest ¶
type MultiStartNewRunnerDutySpecTest struct { Name string Tests []*StartNewRunnerDutySpecTest }
func (*MultiStartNewRunnerDutySpecTest) GetPostState ¶ added in v0.3.1
func (tests *MultiStartNewRunnerDutySpecTest) GetPostState() (interface{}, error)
func (*MultiStartNewRunnerDutySpecTest) Run ¶
func (tests *MultiStartNewRunnerDutySpecTest) Run(t *testing.T)
func (*MultiStartNewRunnerDutySpecTest) TestName ¶
func (tests *MultiStartNewRunnerDutySpecTest) TestName() string
type StartNewRunnerDutySpecTest ¶
type StartNewRunnerDutySpecTest struct { Name string Runner ssv.Runner Duty *types.Duty PostDutyRunnerStateRoot string PostDutyRunnerState types.Root `json:"-"` // Field is ignored by encoding/json OutputMessages []*types.SignedPartialSignatureMessage ExpectedError string }
func (*StartNewRunnerDutySpecTest) GetPostState ¶ added in v0.3.1
func (test *StartNewRunnerDutySpecTest) GetPostState() (interface{}, error)
func (*StartNewRunnerDutySpecTest) Run ¶
func (test *StartNewRunnerDutySpecTest) Run(t *testing.T)
func (*StartNewRunnerDutySpecTest) RunAsPartOfMultiTest ¶ added in v0.3.1
func (test *StartNewRunnerDutySpecTest) RunAsPartOfMultiTest(t *testing.T)
RunAsPartOfMultiTest runs the test as part of a MultiMsgProcessingSpecTest. It simply runs without calling oveerideStateComparison
func (*StartNewRunnerDutySpecTest) TestName ¶
func (test *StartNewRunnerDutySpecTest) TestName() string