Manual Assignment:

CASA is building a web application to create and manage meetings.

There are two screens to create and list meetings.
You are expected to come up with cases separately for api testing, web automation and
manual testing.
The details of the screens are listed below.

Create Meeting Screen:

- name
- start time (date & time)
- end time (date & time)
- users -> multiselect (listed from user listing API)
- meeting type -> select (options: discussion, catch up, demo)

List Meeting Screen:

- filters
* search by name
* from date (date only), to date (date only) -> (list meetings between the days by
using start time and end time)
* filter by meeting type (dropdown)
- apply & clear button for filters
- list of meetings ('no meetings available' text will be displayed otherwise)
Web Automation testing:

Write web automation for JWT website.

The data needed for web automation is given. Use data within backticks.
Examples are provided to understand the functioning of the website. Those are the only
parts in the website you'll be automating. Research on the same if you're unclear.
Come up with your own cases and automate tests.

link: `https://jwt.io`
token:
`eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhIjoxLCJiIjoyLCJjIjozLCJpYXQiOjE2OTYzOTc5Mj
d9.6S9s1qxsu454fCUtOOME3Y_LLw7jq1owBleccDmPwvo`
secret: `helloworld`

Example 1:
1. Go to the link.
2. Paste the token in the Embedded text area.
3. Assert if the value of "c" is 3 in the payload.
4. Assert if you're getting 'Invalid Signature' under the Embedded text area.

Example 2:
2. Go to the link.
3. Paste the token in the Embedded text area.
4. Assert if you're getting 'Invalid Signature' under the Embedded text area.
5. Paste the secret in the input under verify signature.
6. Assert if you're getting 'Signature Verified' under the Embedded text area.
7. Assert if the token is the same as the one you entered.
8. Assert if the value of "c" is still 3.
9. Assert if changing the secret changes the token but the payload remains the same.