Hints for MeetingScheduler\

General Hint 1:

There are 2 rules that are failing regardless of the implementation. They will fail on the correct implementation as well. Can you spot them? The next general hints will refer to these rules.

General Hint 2:

Run the rule checkStartedToStateTransition on one of the implementations that you've already fixed. It still fails. Follow the values in the assertion closely, particularly the explicit values of the states, are they checking what the rule wants them to check?

General Hint 3:

Run the rule monotonousIncreasingNumOfParticipants on one of the implementations that you've already fixed. It still fails. Look at the failing method, how come before creating a meeting the number of participants was greater than 0? Go back to BankLesson1 and refresh yourself about the failure in TotalGreaterThanUser.spec and its mitigation (precondition).

MeetingSchedulerBug1.sol

Hint:

What's the assert failing here on the rule startOnTime? What are the variables that are checked against each other in the inequalities and what are their values?

MeetingSchedulerBug2.sol

Hint:

Why is the assertion failing on endMeeting? Are the uint8 values of the enumerable match their expected values?

MeetingSchedulerBug3.sol

Hint:

In the world of MeetingScheduler, the shortest meeting is at least 1 second. What are the values of the variables checked in the assertion?

MeetingSchedulerBug4.sol

Hint 1:

Before you fix the code you need to find another problem that lies in another file. See General Hints 1 + 2 for more help on that.

Hint 2:

Now that you've fixed the problem with the rule, does it make sense that the condition fails on joinMeeting?

This is an addition after the bare clone

This is a try after a PR on the private repo