Sign up to access "Laravel Teams" right now.

And of course, we'll go ahead and update our tests to make sure that these get removed. Okay, so I've gone ahead and just cleared everything out of the database. I've got two users, Alex and Mabel, both just with their own personal teams. The first thing I'm going to do is go ahead and invite Mabel to this team.

So let's go ahead and pull her in and send an invite. Let's go over to our email client, grab the invitation link here and go ahead and paste it in. And everything looks good. Mabel is a member of this team and she is a team member. Now, if we go ahead and remove her from this team, so let's go ahead and remove her from this team.

In fact, the consequence of this is if we change her role to an admin and hit save, then we go ahead and remove her from this team. She is removed, so she no longer has access. But let's say a little bit later on, we want to go ahead and add her back in.

Let's do that now. So let's add her back into the team. And we're kind of expecting her to just be added as a member as we've set up and written in our test. So let's go ahead and do this again and grab the new invite, grab the link and paste that into her account. She's now part of that team. But look what's happened.

She is a team member, but also a team admin. So remember, we can have multiple roles per user, although we're just kind of sticking with single roles. And of course, you can adjust that. OK, so the consequence of this is if a member is added again, who was previously an admin, but you just wanted them to be a member or another role,

then this is just going to keep adding roles on as long as they're unique. OK, let's go ahead and write a test for this just so we can get this to fail. And then we will go ahead and fix this up. So we come over to our team member controller test. Let's go and have a look. It can remove a member from the team.

This should, once we run this test, get rid of their team member role. Now, we can't really test roles in here at the moment because we haven't set a current team. So what we can do up here is go ahead and set the permissions team ID within our test to the user's current team ID. So that will do all of the adding of roles and everything that we need in the context of the team that we are testing.

And then we can go ahead and obviously acting as that user, delete that user from the test. We want to make sure, as well as all of this stuff, that they don't have that role. So we can say and member and we can grab them fresh out the database roles and count. Or we could say roles to have count. It's up to you. So to have count.

And we just want them to have a zero count role. We don't want them to have a role within the context of this team. Let's just go ahead and die dump on this first, just so we can make sure that we are heading in the right direction. So let's go ahead and grab the count from here first of all. And let's go ahead and run this test in isolation. So let's go ahead and say pest filter and can remove a member from the team.

We get zero. Now, let's just have a look. Right. OK. So the reason we get zero is because we didn't assign a role to this user. Remember, with our tests, we're not hitting an end point to add the user. So we're not getting the benefit of all of this stuff that would normally happen. So let's go and attach this user with a role and then make sure it's deleted as part of that request.

Of course, what you could do as well is as part of your test, you could make a separate HTTP request to add the user first. Or you could do all of this set up manually within your test. I prefer doing this set up manually so I can adjust things, but it's entirely up to you. So we're going to go ahead and say assign role and we're going to assign the team admin role to start with.

And then we're going to make sure that team admin role is is gone. So let's go ahead and run that test again and we get one. So at this point here, we should have detached the role, but it's still the count of one. So you could do your test however you want. You could say that you want them to have zero roles or you could say that you want to make sure they don't have a specific role.

It's entirely up to the way you're building this. But the main point is when we run this, this fails because their role is hanging around still. So all we need to do is come over to our team member controller. And we need to when we remove them, we want to detach all of their roles. So to do that, we just need to say user roles and detach and should be good.

Let's go over and run our test again. And sure enough, we get green. So I'm not going to go through the whole UI flow again here. But we now know that when a team member is removed from the team, their roles get detached, which means that when they're re-added, they're not going to end up with any of the previous roles that they had hanging around.