Switching between `test_case_insecure` may cause weird behavior

Open
#127 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
testing

Research direction

Search for the test_case_user() method and inspect the user_info object it returns when test_case_insecure is True. Confirm that user_id is absent in this path, add it to the returned object, and verify that the insecure test-case behavior now includes the identifier without affecting production behavior.

Written by the indexing model from the issue text.

Description

good first issue python

The user_id is missing from the test_case_user() method. This is used when test_case_insecure is set to True. This should not impact production servers. This may be a super easy fix by adding user_id to the returned user_info object.

Dominant language
Python
Stars
12
Forks
11
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ArgLab/writing_observer

All issues in ArgLab/writing_observer

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.