Solution to Challenge 1 - Login with Different Users
The article presents a solution to a testing challenge involving user login with different roles and languages using API automation tools. The author demonstrates approaches with Postman and .NET frameworks, emphasizing reusable functions and test organization. Different user types, such as admin and normal users, are tested for proper access control and response handling.
- ▪The challenge involves testing login functionality with different user roles and languages, where user role determines the menu displayed.
- ▪API tests were implemented using Postman and .NET with RestSharp, focusing on modularity and reuse through global utility functions.
- ▪Test scenarios include valid and invalid logins, menu access based on user role, and validation of access tokens and response status codes.
- ▪The author uses CSV files for data-driven testing and integrates tests into CI/CD pipelines using tools like Newman and Azure DevOps.
- ▪Security practices include storing credentials as secrets rather than in code, using systems like Azure Key Vault.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 1660045) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } abigail armijo Posted on May 16 Solution to Challenge 1 - Login with Different Users #playwright #api #automation #testing Abi's Testing Dojo (2 Part Series) 1 Practice Real-World Testing Scenarios for QA: Challenge 1 - Login with Different Users 2 Solution to Challenge 1 - Login with Different Users Challenge #1 is done — here's my solution to Practice Real-World Testing Scenarios for QA: Challenge #1 - Login with Different Users I created the Abi's testing dojo, a website with…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).