Skip to content

Live Tests

Live tests are automatic checks that use the real Slipmat site in a real browser, the same way people do. They run after every Slipmat update, and the team gets an alert when one fails. The tests use hidden test accounts that other people never see.

  • An artist runs a scheduled event from warmup to the end, with three listeners at the same time: a logged-in listener, a roadie on a phone, and a listener who is not logged in.
  • The music plays for every listener, and nothing on the page stops it: chat, polls, song requests, a technical hold, the end of the event, and a resume.
  • Listeners who arrive in warmup and listeners who arrive later get every chat message. So does the roadie after coming back in a new browser.
  • Hype and poll votes reach the artist and the other listeners.
  • The test stream has low video quality. The Stream Dashboard warns about the video and not about the sound, and the music plays.
  • The audience list shows each person once, also a person who has the page open on two devices, and it counts the listener who is not logged in.
  • The roadie can hide a chat message for everyone and talk with the artist in the private crew chat. Other listeners can do neither and never see the crew chat.
  • The artist’s live URL opens the event.
  • Ending the event closes song requests for every listener.
  • The listener who is not logged in also sees the event start, pause for a technical hold, end and resume.
  • When the stream goes down, new listeners, also one who is not logged in, can still open the live page, both during a technical hold and after it. They see the hold message or the connection problem, and the logged-in listener can chat.
  • An imported Track Collection is ready for requests at once, with song details for every song that Slipmat’s music database already knows.
  • Listeners can find, request and vote for songs, add a message or a shout-out, and withdraw a request.
  • The artist can handle every request and shout-out on the Stream Dashboard, and listeners see the result.
  • The artist can switch a request to another track, such as the version that the listener’s message asks for. The request stays open, and Now Playing shows the track that the artist switched to.
  • The artist can add requests for people who asked in person.
  • The request limit, and turning requests off and on, reach the listeners.
  • An artist creates a request event, and visitors can request with or without an account.
  • Signing up with Google or Apple from a request event asks only for a username, and the visitor’s earlier requests move to the new account.
  • Logging in again with Google or Apple opens the same account.
  • Signing up with Google anywhere else asks for the full profile.
  • The /topic command changes the channel topic, and the chat shows the change.
  • When the server refuses a chat command, the chat shows an error.
  • Logging in with email and password opens the account.
  • A photo from an iPhone can be the profile photo, and it is still there after a reload.
  • Profile details are saved and still there after a reload.
  • Cleared details stay cleared, and choosing another country removes the city. Other people see the change on the profile card.
  • Bad input shows an error at the right field, and nothing is saved. After a failed save, the typed details stay, and the next try saves them.
  • During a live event, the /profile chat command opens the profile for editing, and the music keeps playing. Closing it without saving changes nothing. Other people see a saved change at once on an open profile card and in the audience list.

Artists who come back from the old Slipmat

Section titled “Artists who come back from the old Slipmat”
  • A rejoin link brings back the account, the artist profile, the old events, and the public artist page at the old slug, in one step.
  • The Artist Dashboard shows the first steps, and marks each step done after the artist does it: scheduling defaults, a soundcheck, and the first published event.
  • A Show made from the first steps starts on the day and hour of the scheduling defaults.
  • A rejoin link that was already used shows a way to log in instead of the form.
  • An expired rejoin link can be renewed into a working one.
  • Bad input on the rejoin form shows an error at the right field, and the link keeps working.
  • Profile details, scheduling defaults and booking contacts are saved and still there after a reload.
  • Links typed without https://, and tags with spaces or capitals, are cleaned up and saved.
  • Bad input shows an error at the right field, and nothing is saved.
  • A name that another artist uses is refused.
  • The artist photo and the default event photo upload and show after a reload.
  • Unsupported or too large images are refused before they upload.
  • The first visit asks for scheduling defaults, and the schedule form then offers them first. Closing the question without saving asks again on the next visit.
  • An event with everything set can be published: photo, tags, description, unlisted, song requests and tips.
  • A draft can be saved without a date, and it keeps everything that was set.
  • Bad input shows an error at the right field, and nothing is saved.
  • Tags and slugs are cleaned up: Deep-House becomes deephouse, and My Event! becomes my-event.
  • A slug or a start time that another event already has is refused.
  • Changes are saved, and the form shows them when it opens again. Cleared details stay cleared.
  • Bad input shows an error at the right field, and nothing is saved.
  • A draft can be published after it gets a start time.
  • Dates can be proposed to listeners, and each date needs a starting hour.
  • Changes and new dates are saved. Bad input shows an error, and nothing is saved.
  • An event can be created from a proposed date, and it starts at that time.
  • Artists enter times in the artist’s timezone. Everyone sees them in their own timezone: the browser’s, or the one saved in their account profile.
  • The schedule form names the artist’s timezone only when it is not the viewer’s timezone.
  • When the artist changes timezone, events keep their start time.