> Needs fixing:
>
> Missing acceptance tests - I suppose something similar to:
> "TEST_F(PromptSessionClientAPI, notifies_start_and_stop)"
>
>
> ===
> 733 + // Need to verify explicitly as we see unmatched callbacks during
> teardown of fixture
> 734 + Mock::VerifyAndClearExpectations(&prompt_session_listener);
> ===
> Not needed.
>
> ===
> 716 // Need to verify explicitly as we see unmatched callbacks during
> teardown of fixture
> 717 Mock::VerifyAndClearExpectations(&prompt_session_listener);
> ===
> Pre-existing, but not needed either.
>
> ===
> 198 + std::unique_lock<std::mutex> lk(guard);
> 210 + std::unique_lock<std::mutex> lk(guard);
> 222 + std::unique_lock<std::mutex> lk(guard);
> 234 + std::unique_lock<std::mutex> lk(guard);
> ===
> Prefer std::lock_guard<std::mutex> as no features of unique_lock are used.
>
> ===
> 605 +TEST_F(PromptSession, start_prompt_session_when_stopped)
> 616 +TEST_F(PromptSession, stop_prompt_session_when_started)
> 628 +TEST_F(PromptSession, suspend_prompt_session_when_started)
> 640 +TEST_F(PromptSession,
> suspend_prompt_session_fails_to_stop_helper_when_not_started)
> 650 +TEST_F(PromptSession, resume_prompt_session_when_suspended)
> 663 +TEST_F(PromptSession,
> resume_prompt_session_fails_to_stop_helper_when_not_started)
> ===
> Redundant prompt_session in test case name
> Perhaps something like:
>
> TEST_F(PromptSession, can_start)
> TEST_F(PromptSession, can_stop)
> TEST_F(PromptSession, can_suspend)
> TEST_F(PromptSession, fails_to_suspend_if_not_in_started_state)
> TEST_F(PromptSession, can_resume)
> TEST_F(PromptSession, fails_to_resume_if_in_stopped_state)
Done.
>
> ===
> 204 + helper_session->start_prompt_session();
> ===
> e. al. Do you need to keep the mutex locked while making these calls?
> Preferably, unlock the mutex before making them (in which case disregard the
> suggestion for std::lock_guard above).
If we don't then we can end up interleaving calls to start/stop/suspend.
> Needs fixing: PromptSessionCl ientAPI, notifies_ start_and_ stop)" ClearExpectatio ns(&prompt_ session_ listener) ; ClearExpectatio ns(&prompt_ session_ listener) ; lock<std: :mutex> lk(guard); lock<std: :mutex> lk(guard); lock<std: :mutex> lk(guard); lock<std: :mutex> lk(guard); guard<std: :mutex> as no features of unique_lock are used. PromptSession, start_prompt_ session_ when_stopped) PromptSession, stop_prompt_ session_ when_started) PromptSession, suspend_ prompt_ session_ when_started) PromptSession, prompt_ session_ fails_to_ stop_helper_ when_not_ started) PromptSession, resume_ prompt_ session_ when_suspended) PromptSession, prompt_ session_ fails_to_ stop_helper_ when_not_ started) PromptSession, can_start) PromptSession, can_stop) PromptSession, can_suspend) PromptSession, fails_to_ suspend_ if_not_ in_started_ state) PromptSession, can_resume) PromptSession, fails_to_ resume_ if_in_stopped_ state)
>
> Missing acceptance tests - I suppose something similar to:
> "TEST_F(
>
>
> ===
> 733 + // Need to verify explicitly as we see unmatched callbacks during
> teardown of fixture
> 734 + Mock::VerifyAnd
> ===
> Not needed.
>
> ===
> 716 // Need to verify explicitly as we see unmatched callbacks during
> teardown of fixture
> 717 Mock::VerifyAnd
> ===
> Pre-existing, but not needed either.
>
> ===
> 198 + std::unique_
> 210 + std::unique_
> 222 + std::unique_
> 234 + std::unique_
> ===
> Prefer std::lock_
>
> ===
> 605 +TEST_F(
> 616 +TEST_F(
> 628 +TEST_F(
> 640 +TEST_F(
> suspend_
> 650 +TEST_F(
> 663 +TEST_F(
> resume_
> ===
> Redundant prompt_session in test case name
> Perhaps something like:
>
> TEST_F(
> TEST_F(
> TEST_F(
> TEST_F(
> TEST_F(
> TEST_F(
Done.
> session- >start_ prompt_ session( );
> ===
> 204 + helper_
> ===
> e. al. Do you need to keep the mutex locked while making these calls?
> Preferably, unlock the mutex before making them (in which case disregard the
> suggestion for std::lock_guard above).
If we don't then we can end up interleaving calls to start/stop/suspend.