Lines Matching refs:be
52 does not change the semantic state of the object, so it can be called on a existing
53 component that will used further on. Note: This can be a strong test limitation.
56 the name of the test. Must be an interface, service, or implementation name.
60 The instance to be tested.
71 This test changes the state of the object. The object may be useless
73 be called multiple times with a new test object instance. Note: Each test
74 scenario should be independent of each other, so even if a scenario
75 didn't pass the test, the other test can still be performed.
79 The name of the test. Must be an interface, service, or
83 The instance to be tested.
101 a test using several threads but that this test method should be designed
102 to be called by several threads. So for example, it has to take into consideration
103 that a test object state that is changed by the method can be
105 expected state can't be confirmed after setting it. Besides that, everything
109 component to be tested this method should not be implemented (it should
111 needs of testing this component should be integrated in the test method.
114 The name of the test. Must be an interface, service or
118 The instance to be tested.
133 /** registers an event listener, which will be called for reporting