There are various ways Stream and BuddyPress can be activated in a multisite.

BuddyPress

These are outlined here.

• Network activated:
  • BuddyPress root blog is the main site where the network admin is
  • BuddyPress root blog is not the main site
• Not network activated
  • on a blog
  • not on a blog

(nb: I know the last two are obvious but they're needed for record keeping 😊)

Stream

• Network activated (always on main site with network admin)
  • Site access enabled, all sites can see their own Stream logs
  • Site access disabled
• Enabled on a single site only

For Stream, testing the network admin logs as well as the individual site logs is be enough.

So let's test these scenarios:

• BuddyPress network activated root blog is the main site
• Stream network activated in the network admin
• Stream activated on the root blog
• BuddyPress root blog is not the main site
• Stream network activated in the network admin
• Stream activated on the site on which BuddyPress has set as the root blog
• Stream activated on a site where BuddyPress is not activated (mainly for completeness)

Note regarding the tests above: if you are viewing the Stream logs as an admin of a site in a multisite and are not a super admin, you can't edit BuddyPress so the action links will not be shown.

• BuddyPress is not network activated but is activated on one site
• Stream network activated in the network admin
• Stream activated on a site where BuddyPress is activated
• Stream activated on a site where BuddyPress is not activated (it doesn't show up, this is correct)

The BuddyPress connector won't add links if the functions used to generate them aren't available (see #1517 ) so in the network admin area, if BuddyPress is not network activated, the expectation is that there won't be action links before the log entries. This is acceptable.