This really depends on the team. Each time should determine, together, what details are needed for user stories. I've worked on a few different teams and each team has had a slightly different variation of detail. The most important thing is that user stories are sliced to deliver interactive value to the user.
You never want to write user stories to the level of detail where it feels like you're writing tech specs or feature tests. The point of the user story is to describe what the user is trying to accomplish, the job they are trying to get done, or the value they are looking for.