zulip/frontend_tests
Steve Howell f0c99b42ec Rename people.add_in_realm to people.add().
We had this API:

    people.add_in_realm = full-fledged user
    people.add = not necessarily in realm

Now the API is this:

    people.add = full-fledged user
    people._add_user = internal API for cross-realm bots
        and deactivated users

I think in most of our tests the distinction between
people.add() and people.add_in_realm() was just an
accident of history and didn't reflect any real intention.

And if I had to guess the intention in 99% of the cases,
folks probably thought they were just creating ordinary,
active users in the current realm.

In places where the distinction was obviously important
(because a test failed), I deactivated the user via
`people.deactivate`.

For the 'basics' test in the people test suite, I clean
up the test setup for Isaac.  Before this commit I was
adding him first as a non-realm user then as a full-fledged
user, but this was contrived and confusing, and we
didn't really need it for test coverage purposes.
2020-03-22 10:55:11 -07:00
..
casper_lib casper: Use data-stream-id to find checkboxes. 2020-01-28 14:49:57 -08:00
casper_tests docs: Replace casperjs.org links. 2020-02-27 11:03:31 -08:00
node_tests Rename people.add_in_realm to people.add(). 2020-03-22 10:55:11 -07:00
zjsunit node tests: Just set i18n every time. 2020-02-28 17:11:24 -08:00
.eslintrc.json lint: Check eslint indentation for casper tests. 2018-05-06 19:35:18 -07:00
run-casper populate_db, tests: Restrict emails in zulip realm. 2020-03-19 16:21:31 -07:00