Bugs‌ ‌found‌ ‌in‌ WeWork: Flexible Workspace for iOS

WeWork: Flexible Workspace

4.8

WeWork offers access to a global network of professional spaces designed for various work styles. App members can easily book coworking spaces, private offices, or meeting rooms by the hour.

With features like high-speed Wi-Fi and unlimited refreshments, WeWork ensures a conducive work environment. Users can leverage networking opportunities, access data and analytics on workspace usage, and enjoy collaborative experiences at WeWork events. The app offers a new way of working globally, tailored to your specific needs.

We’ve been impressed with how WeWork supports businesses, so we decided to thoroughly test their app to ensure a smooth experience for users. Take a look at our bug report below!

30K+downloads
7.4K ratings

Endless loading page appears when trying to open unavailable desk

Severity:

Critical

Steps to Reproduce:
  1. Navigate to the application.
  2. Search for the unavailable desks.
  3. Open the unavailable desk.
Environment:

iPhone 14 Pro, v. 16.4.1

Actual Result:

“Endless Loading” page is displayed.

Expected Result:

The user should either be able to open an unavailable desk record, or the unavailable desk should be disabled. (The expected behavior depends on the application’s requirements.)

“Auth0” text appears in “Reset Your Password” email

Severity:

Major

Precondition:

The user is on the “My Account” page.

Steps to Reproduce:
  1. Click on the “Edit Profile” link.
  2. Click on the “Reset Password” button.
  3. Check the received email in the mailbox.
Environment:

iPhone 14 Pro, v. 16.4.1

Actual Result:

The extra text reading “auth0” appears in the received email.

Expected Result:

Inappropriate text should not be displayed in the emails.

“Auth0” text appears in “Reset Your Password” email

Missing special characters in password

Severity:

Major

Precondition:

The user is on the “Change Password” page.

Steps to Reproduce:
  1. On the “Change Password” page, enter any password value that does not contain any special characters.
  2. Observe the list of validated password rules.
Environment:

iPhone 14 Pro, v. 16.4.1

Actual Result:

The password rule concerning special characters turns green (implying validity) even when no special characters are present in the entered password.

Expected Result:

The validation of password conditions should be strictly based on the input password value.

Entered credit card number isn't fully displayed

Severity:

Minor

Precondition:

The user is on the page of an available desk.

Steps to Reproduce:
  1. Click on the “Book Desk” button.
  2. Click on the “Add Payment” button.
  3. Enter the card number.
  4. Move the cursor to the “MM/YY” input field.
Environment:

iPhone 14 Pro, v. 16.4.1

Actual Result:

Only the last 4 digits of the entered card number are displayed.

Expected Result:

The entire entered card number should be displayed.

Entered credit card number isn't fully displayed

Invalid phone number validation

Severity:

Minor

Precondition:

The user is on the “Account” page of the app.

Steps to Reproduce:
  1. Click on the “Edit Profile” link.
  2. Input text into the “Phone Number” field.
  3. Click on the “Save” button.
Environment:

iPhone 14 Pro, v. 16.4.1

Actual Result:

The invalid data in the “Phone Number” field is saved.

Expected Result:

A validation message should be displayed for an invalid phone number.

"Add Payment" popup appears behind keyboard

Severity:

Minor

Precondition:

The user is on the main page of the application.

Steps to Reproduce:
  1. Search for any available desk.
  2. Select the desired desk.
  3. Click the “Book Desk” button.
  4. Click the “Add Payment” button.
  5. Place the cursor in the input field.
  6. Remove the existing value.
  7. Click the “<” symbol to close the popup.
  8. Click the “Add Payment” button again.
  9. Place the cursor back in the input field.
Environment:

iPhone 14 Pro, v. 16.4.1

Actual Result:

The “Add Payment” popup is displayed behind the open keyboard.

Expected Result:

The keyboard should be displayed below the “Add Payment” popup, not obscuring it.

Upon testing, I did not encounter any critical issues or glitches that disrupt the primary user experience flows. The app appears to be functioning smoothly and reliably.
Tetiana, QA engineer

Tetiana, QA engineer

Need a reliable QA partner?

Hire us