Skip to content

Path.toBeAnEmptyDirectory #766

@robstoll

Description

@robstoll

Platform (all, jvm, js): all
Extension (none, kotlin 1.3): none

Code related feature

expect(path).toBeAnEmptyDirectory()

//instead of

expect(path)
  .toBeADirectory()
  .feature("findFirstFile", { Files.list(this).use { it.findFirst() } }) {
    isEmpty()
  }

Following the things you need to do:

logic

  • extend PathAssertions with a function toBeEmptyDirectory (see other functions as a guideline)
  • implement toBeEmptyDirectory in DefaultPathAssertions.kt -- bonus use newDirectoryStream instead and list all files as failureHint in case the iterator.hasNext()

api-fluent

  • provide a fun toBeAnEmptyDirectory in a new file called pathExpectations.kt (see for instance isDirectory in pashAssertions.kt as a guideline)
  • add @since 0.16.0 (adapt to current milestone) to KDOC
  • add toBeAnEmptyDirectory to PathExpectationsSpec in specs-common adopt the spec in api-fluent

api-infix

  • provide a fun toBe which expects anEmptyDirectory in a new file called pathExpectations.kt (see toBe aDirectory in pathAssertions.kt as a guideline)
  • add @since 0.16.0 (adapt to current milestone) to KDOC
  • add toBeAnEmptyDirectory to PathExpectationsSpec in specs-common adopt the spec in api-infix

Your first contribution?

  • Write a comment I'll work on this if you would like to take this issue over.
    This way we get the chance to revise the description in case things have changed in the meantime, we might give you additional hints and we can assign the task to you, so that others do not start as well.
  • See Your first code contribution for guidelines.
  • Do not hesitate to ask questions here or to contact us via Atrium's slack channel if you need help
    (Invite yourself in case you do not have an account yet).

Metadata

Metadata

Assignees

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions