# Lesson 3 - Exploring Your Application - A Testing Challenge

**URL:** <https://club.ministryoftesting.com/t/lesson-3-exploring-your-application-a-testing-challenge/40809>\
**Category:** Discussions\
**Tags:** better-operability\
**Created:** [16 July 2020 16:54 UTC](https://club.ministryoftesting.com/t/lesson-3-exploring-your-application-a-testing-challenge/40809 "2020-07-16T16:54:27Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ash\_winter](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/ash_winter/32/1323_2.png) [@ash\_winter](https://club.ministryoftesting.com/u/ash_winter)\
**Post date:** [16 July 2020 16:54 UTC](https://club.ministryoftesting.com/t/lesson-3-exploring-your-application-a-testing-challenge/40809/1 "2020-07-16T16:54:27Z")

</div>

**Title:** Getting to know your application through exploration

**Time:** 30 mins - 1 hour (Or as long as you like to feel comfortable with the application)

**Introduction:** To improve operability we will be making changes to our application. Before making changes, it’s important to understand what the application does and where the risks might be. A great way to do that is to explore the application, using all your testing skills. Let’s focus in on one area to get started, authentication.

**Purpose:** Learn about your application through exploratory testing to build a mental model of how it functions. Using the resources at hand including the Postman collection, your access to the source code and the documentation.

**Activity:**

1. Explore the application to discover:
  - Which of the applications endpoints need admin user privileges to use them.
  - Which endpoints don’t need a token.

2. Write up your findings and add them to the README.md file in your application repo.