Authorization testing in Testing Fundamentals - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Authorization vs Authentication

Which statement best describes the difference between authorization and authentication?

A Authentication and authorization are the same and used interchangeably.

B Authentication verifies who you are; authorization determines what you can access.

C Authorization verifies who you are; authentication determines what you can access.

D Authorization is done before authentication in the login process.

💡 Hint

Think about logging in first, then checking permissions.

Authentication confirms your identity, like entering a password. Authorization checks your rights to access resources after you are identified.

❓ Predict Output

intermediate

Result of Role-Based Access Check

What will be the output of the following Python code simulating a simple authorization check?

Testing Fundamentals

user_role = 'editor'
resource = 'article'

permissions = {
    'admin': ['article', 'comment', 'user'],
    'editor': ['article', 'comment'],
    'viewer': ['article']
}

if resource in permissions.get(user_role, []):
    print('Access granted')
else:
    print('Access denied')

A Access granted

B KeyError

C Access denied

D TypeError

💡 Hint

Check if 'article' is in the list for 'editor' role.

The 'editor' role has permission for 'article', so the condition is true and 'Access granted' is printed.

❓ assertion

advanced

Validating Authorization Failure in Test Assertion

Which assertion correctly tests that a user without 'admin' role cannot delete a user account?

Testing Fundamentals

def can_delete_user(user_role):
    return user_role == 'admin'

user_role = 'viewer'
result = can_delete_user(user_role)

A assert result is False

B assert result == True

C assert result != False

D assert result == None

💡 Hint

The function returns True only for 'admin'. For 'viewer', it returns False.

The assertion must confirm the function returns False for a non-admin role, so 'assert result is False' is correct.

🔧 Debug

advanced

Identify the Bug in Authorization Logic

What is the bug in this JavaScript authorization check code?

Testing Fundamentals

function checkAccess(role) {
  if (role == 'admin') {
    return true;
  } else {
    return false;
  }
}

console.log(checkAccess('viewer'));

A The role variable is not declared.

B The function does not return any value.

C The assignment operator '=' is used instead of comparison '=='.

D The console.log statement is missing parentheses.

💡 Hint

Check the condition inside the if statement carefully.

The code uses '=' which assigns 'admin' to role instead of comparing it. This causes the condition to always be true.

❓ framework

expert

Best Practice for Authorization Testing in Automation Framework

In an automated test framework, which approach best ensures authorization rules are tested effectively?

A Test only happy paths where users have full access to resources.

B Test authorization only after deployment to production.

C Skip authorization tests and rely on manual testing for security.

D Use parameterized tests to check multiple roles against resource access permissions.

💡 Hint

Think about covering different user roles and permissions efficiently.

Parameterized tests allow running the same test logic with different roles and resources, ensuring broad coverage of authorization rules.

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