move new_entry tests to their own section

Open
  • Is something wrong?
#6 1 comment 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@brass75 is already working on this.

Since Jun 21, 2025.

Assessment

This issue has not been assessed yet.

Description

With the CLI it may be an easier to understand approach to move the commands to their own files.

Justification:

  • render-engine init is in its own file
  • render-engine tools are in their own file
  • The act of calling render-engine cli are in its own file

New entry is spread across two files test_cli.py and test_cli_commands.py

This may be bigger task that is move each of the commands to their own test file (which could require moving and calling things in different locations)

Solution:

  • Create tests_render-engine-new_entry.py
  • Moved all tests involving new entry in to those locations
Dominant language
Python
Stars
4
Forks
8
Avg merge
21h 34m
Merged PRs (30d)
10

Getting set up

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 render-engine/render-engine-cli

All issues in render-engine/render-engine-cli

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.