Ebazhanov/cypress-ui-api-tests

Implement changes based on the provided feedback

Open

#1 opened on Jun 15, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)TypeScript (0 forks)github user discovery
good first issue

Repository metrics

Stars
 (2 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Feedback:

ask 1:

  • simple structure and readability ~ very basic functional and not functional testing coverage ~ findings reported, although info is minimal (no proper description, steps to reproduce, additional info like screenshots/video..)
  • No reasoning for the priority set
  • No risks analysis

Task 2:

  • Simple implementation of the UI task
  • use of beforeEach to handle repetitive actions
  • coverage of core operations
  • Improvable readability
  • No clean project structure (tasks are mixed in the same folder, many files in the main root that should be moved to dedicated task’s folder.
  • Missing dedicated Readme addressing the challenge’s requirements
  • Hardcoded values
  • Tests are dependent on each other for their correct execution.

Task 3:

  • use of custom commands
  • Core functionality coverage
  • use of dynamic names
  • assertion of API response
  • utility functions used
  • parameterisation of commands
  • no error handling
  • Tests are dependent on each other
  • Hardcoded values

Contributor guide

Research direction
Review the provided feedback and prioritize addressing the issues: improve project structure, add error handling, remove hardcoded values, ensure tests are independent, and create a README. Start by analyzing the current codebase against the feedback points.
Tech stack
typescriptcypress
Domain
testing
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitTypeScriptCypress
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60