Authorization testing in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to check if a user has admin rights.

Testing Fundamentals

if user.role == [1]:
    access_granted = True

Drag options to blanks, or click blank then click option'

A"guest"

B"admin"

C"user"

D"anonymous"

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'guest' or 'user' instead of 'admin' will not grant admin access.

The code checks if the user's role is exactly "admin" to grant access.

2fill in blank

medium

Complete the code to deny access if the user is not authorized.

Testing Fundamentals

if not user.is_authorized():
    [1] = False

Drag options to blanks, or click blank then click option'

Auser_role

Baccess_denied

Caccess_granted

Dpermission_level

Attempts:

3 left

💡 Hint

Common Mistakes

Setting 'access_denied' instead of 'access_granted' may cause confusion in logic.

Setting access_granted to False denies access when the user is not authorized.

3fill in blank

hard

Fix the error in the authorization check to correctly verify user permissions.

Testing Fundamentals

if "edit" [1] user.permissions:
    allow_edit = True

Drag options to blanks, or click blank then click option'

Ain

B!=

Cnot in

D==

Attempts:

3 left

💡 Hint

Common Mistakes

Using '==' instead of 'in' causes the check to fail if permissions is a list.

Using in checks if "edit" is among the user's permissions.

4fill in blank

hard

Fill both blanks to create a test that asserts unauthorized users cannot access admin pages.

Testing Fundamentals

def test_admin_access(user):
    assert user.role [1] "admin"
    assert access_to_admin_page(user) [2] False

Drag options to blanks, or click blank then click option'

A!=

B==

Cis

Dis not

Attempts:

3 left

💡 Hint

Common Mistakes

Using '==' instead of '!=' for role check allows admins only.

The test asserts the user role is not 'admin' and that access is denied (False).

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps users to their access status based on role.

Testing Fundamentals

access_map = {user.name: True if user.role [1] "admin" [2] True [3] False for user in users}

Drag options to blanks, or click blank then click option'

A==

Bif

Celse

D!=

Attempts:

3 left

💡 Hint

Common Mistakes

Using '!=' instead of '==' reverses the logic.

Omitting 'else' causes syntax errors.

The comprehension assigns True if the user's role is 'admin', else False.

Practice

1. What is the main goal of authorization testing in software applications?

easy

A. To find syntax errors in the code

B. To verify users can only access allowed resources

C. To test the speed of the application

D. To check if the software installs correctly

Solution

1. Step 1: Understand the purpose of authorization testing

   Authorization testing checks if users have permission to access certain parts of the system.

2. Step 2: Differentiate from other testing types

   Unlike installation or speed tests, authorization focuses on access control.

3. Final Answer:

   To verify users can only access allowed resources -> Option B

4. Quick Check:

   Authorization = Access control [OK]

Hint: Authorization means checking user access rights [OK]

Common Mistakes:

• Confusing authorization with authentication
• Thinking it tests software installation
• Mixing it with performance testing

2. Which of the following is the correct way to test if a user with role guest cannot access the admin page?

easy

A. Assert that accessing admin page returns status code 403

B. Assert that accessing admin page returns status code 200

C. Assert that the page loads without any error

D. Assert that the user can edit admin settings

Solution

1. Step 1: Identify expected behavior for unauthorized access

   A guest user should be denied access, usually indicated by HTTP status 403 (Forbidden).

2. Step 2: Match assertion with expected status code

   Checking for status 403 confirms access is blocked correctly.

3. Final Answer:

   Assert that accessing admin page returns status code 403 -> Option A

4. Quick Check:

   Unauthorized access = status 403 [OK]

Hint: 403 means forbidden access, use it to test denial [OK]

Common Mistakes:

• Using status 200 which means success
• Ignoring error codes and only checking page load
• Testing edit rights for guest users

3. Consider this test code snippet for authorization:

def test_access(user_role):
    if user_role == 'admin':
        return 'Access granted'
    else:
        return 'Access denied'

result = test_access('guest')

What is the value of result after running this code?

medium

A. 'Access denied'

B. 'Access granted'

C. None

D. Error

Solution

1. Step 1: Analyze the function logic for 'guest' role

   The function returns 'Access granted' only if user_role is 'admin'. For 'guest', it returns 'Access denied'.

2. Step 2: Check the returned value for 'guest'

   Since 'guest' is not 'admin', the else branch runs, returning 'Access denied'.

3. Final Answer:

   'Access denied' -> Option A

4. Quick Check:

   Guest role = Access denied [OK]

Hint: Only admin gets access; others denied [OK]

Common Mistakes:

• Assuming guest has access
• Confusing return values
• Expecting None or error instead of string

4. You wrote this test to check if a user with role editor can access the edit page:

def test_editor_access():
    response = access_page('edit', 'editor')
    assert response.status_code == 200
    assert response.content == 'Access denied'

What is wrong with this test?

medium

A. It uses wrong role name 'editor'

B. It should assert status code 404 instead

C. It misses checking the response headers

D. It asserts success status but expects denial content

Solution

1. Step 1: Understand assertion conflict

   The test expects status code 200 (success) but also expects content 'Access denied', which is contradictory.

2. Step 2: Identify correct assertion logic

   If access is denied, status code should not be 200; usually 403 or similar. The test mixes success code with denial message.

3. Final Answer:

   It asserts success status but expects denial content -> Option D

4. Quick Check:

   Status 200 means success, can't deny access [OK]

Hint: Status and content must match access result [OK]

Common Mistakes:

• Mixing success status with denial message
• Ignoring role correctness
• Assuming 404 for access denial

5. You have three user roles: admin, editor, and viewer. The editor can edit content but cannot access user management. Which test case best verifies this authorization rule?

hard

A. Test that viewer can edit content

B. Test that editor gets 200 on user management page

C. Test that editor can access edit page and gets 403 on user management page

D. Test that admin cannot access edit page

Solution

1. Step 1: Identify editor permissions

   Editor role should have access to edit content but be denied access to user management.

2. Step 2: Match test case to permissions

   Testing editor access to edit page (expect success) and user management page (expect 403 forbidden) verifies the rule correctly.

3. Final Answer:

   Test that editor can access edit page and gets 403 on user management page -> Option C

4. Quick Check:

   Editor edits allowed, user mgmt denied [OK]

Hint: Test allowed and denied pages per role [OK]

Common Mistakes:

• Testing wrong permissions for roles
• Expecting viewer to edit content
• Assuming admin cannot edit content