Skip to content

move new_entry tests to their own section #6

@kjaymiller

Description

@kjaymiller

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions