1) test when a user chooses 'mob' from the homepage, they are added to a single shared Jitsi (Paironauts.AcceptanceTest)
test/browser/acceptance_test.exs:21
** (Wallaby.ExpectationNotMet) Expected to find 1, visible element that matched the css '#meet' but 0, visible elements were found.
code: |> assert_has(css("#meet", visible: true))
stacktrace:
test/browser/acceptance_test.exs:27: (test)
2) test when two users choose 'pair' from the homepage, they are added to a Jitsi (Paironauts.AcceptanceTest)
test/browser/acceptance_test.exs:31
Expected truthy, got false
code: assert has_text?(click(visit(session1, "/"), css("#pair")), "Waiting for pair partner")
stacktrace:
test/browser/acceptance_test.exs:36: (test)
3) test user on home page who hasn't chosen to pair is not pulled into pairing session (Paironauts.AcceptanceTest)
test/browser/acceptance_test.exs:69
** (Wallaby.ExpectationNotMet) Expected to find 1, visible element that matched the css '#wait' but 0, visible elements were found.
code: |> assert_has(css("#wait", text: "Waiting for pair partner..."))
stacktrace:
test/browser/acceptance_test.exs:73: (test)
we're not sure why - these are some that have failed locally at some point, but they are currently passing for some locally (e.g. @praveendhawan ) while others (e.g. @SherSpock and @tansaku) have a different js failure (see https://github.com/jitsi/jitsi-meet/issues/2852)
CI currently fails with these errors:
https://circleci.com/gh/AgileVentures/Paironauts/17?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link
we're not sure why - these are some that have failed locally at some point, but they are currently passing for some locally (e.g. @praveendhawan ) while others (e.g. @SherSpock and @tansaku) have a different js failure (see https://github.com/jitsi/jitsi-meet/issues/2852)