The following state diagram is given as basis for state transition testing and contains only valid transitions:
Explanation of the state diagram: States are depicted as nodes. The initial state is I, the final state is F. A state transition is depicted as a directed arrow with the initiating event as a label, e. g. from I to S1 with event a, and is also written as a triple (I,a,S1). Note: A test case is a sequence of events that initiates the corresponding sequence of state transitions.
The state diagram contains the following 7 state transitions:
(I, a, S1)
(S1, a, S2), (S1, b, S3), (S1, c, F)
(S2, a, S3)
(S3, a, S2), (S3, b, F)
What is the minimum number of test cases to achieve 100% coverage of all valid state transitions in the diagram?
Which of the following is a good testing practice which is applicable INDEPENDENT of the software development lifecycle followed?
Consider the following user story and its acceptance criteria:
User Story:
As a member of the "Agnotoly" association, I want to be able to pay the association’s dues through an automatic payment method so that I can forget about payment deadlines.
Acceptance Criteria:
The member can only pay with ‘Agnesis Master’ credit card.
The member must register their cell phone number.
The member must register the credit card in the payment system.
The member must select a payment method (monthly or annual).
The member must accept the terms and conditions for the selected method.
If terms and conditions are accepted, the system sends an OTP (one-time password) to the member’s phone for verification.
The payment method is registered only after OTP verification.
Once the payment method is registered, the system will charge on the first business day of the following month.
Test Cycle Results:
Members successfully paid dues using the credit card.
Payments were processed monthly and for over a year.
Which ONE of the following options identifies the acceptance criteria that has NOT been fully covered?
Which of the following activities are part of test planning?
I) Setting the entry and exit criteria
II) Determining the validity of bug reports
III) Determining the number of resources required
IV) Determining the expected result for test cases