Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unit testing tracking issue #71

Open
53 of 99 tasks
Anders429 opened this issue Mar 20, 2022 · 0 comments
Open
53 of 99 tasks

Unit testing tracking issue #71

Anders429 opened this issue Mar 20, 2022 · 0 comments
Labels
C - Testing Category: Verifying the correctness of code. C - Tracking Issue Category: Tracking the progress and completion of a feature.

Comments

@Anders429
Copy link
Owner

Anders429 commented Mar 20, 2022

This is a tracking issue for complete unit testing of the code base. As modules have unit tests written for them, they will be checked off the following list.

  • archetype
    • identifier
      • impl_serde.rs
      • iter.rs
      • mod.rs
    • impl_debug.rs
    • impl_drop.rs
    • impl_eq.rs
    • impl_send.rs
    • impl_serde.rs
    • mod.rs
  • archetypes
    • impl_debug.rs
    • impl_eq.rs
    • impl_serde.rs
    • iter.rs
    • mod.rs
    • par_iter.rs
  • entities
    • seal
      • length.rs
      • mod.rs
      • storage.rs
    • mod.rs
  • entity
    • allocator
      • impl_serde.rs
      • location.rs
      • locations.rs
      • mod.rs
      • slot.rs
    • identifier
      • impl_serde.rs
      • mod.rs
    • seal
      • mod.rs
      • storage.rs
    • mod.rs
  • query
    • filter
      • mod.rs
      • seal.rs
    • result
      • iter.rs
      • mod.rs
      • par_iter.rs
    • view
      • par
        • seal
          • mod.rs
          • repeat.rs
        • mod.rs
      • assertion_buffer.rs
      • mod.rs
      • seal.rs
    • claim.rs
    • mod.rs
  • registry
    • seal
      • assertions.rs
      • length.rs
      • mod.rs
      • storage.rs
    • debug.rs
    • eq.rs
    • mod.rs
    • send.rs
    • serde.rs
    • sync.rs
  • system
    • schedule
      • raw_task
        • mod.rs
        • seal.rs
      • stage
        • mod.rs
        • seal.rs
      • builder.rs
      • mod.rs
      • sendable.rs
      • task.rs
    • mod.rs
    • null.rs
    • par.rs
  • world
    • entry.rs
    • impl_debug.rs
    • impl_default.rs
    • impl_eq.rs
    • impl_send.rs
    • impl_serde.rs
    • impl_sync.rs
    • mod.rs
  • component.rs
  • doc.rs
  • hlist.rs
  • lib.rs
  • macro.rs
  • reexports.rs

From this point forward, all pull requests should include unit tests for everything added. This wasn't included in the past due to the experimental nature of things, but now that this is shaping into a real library tests need to be included from the get-go.

@Anders429 Anders429 added C - Tracking Issue Category: Tracking the progress and completion of a feature. C - Testing Category: Verifying the correctness of code. labels Sep 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C - Testing Category: Verifying the correctness of code. C - Tracking Issue Category: Tracking the progress and completion of a feature.
Projects
None yet
Development

No branches or pull requests

1 participant