Cosmos: Can we force separation of test file and sources?

Created on 2 Dec 2017  路  7Comments  路  Source: OpenGenus/cosmos

This is a(n):

  • [ ] New algorithm
  • [ ] Update to an existing algorithm
  • [ ] Error
  • [x] Proposal to the Repository

Details:

Since this project is a lib, one can use source code to create his / her code, but these files do not include the necessary code, but also the test code and the header files it uses, but one may not want these .

Most helpful comment

Solved.

All 7 comments

This will be a nice addition.
It is important to enable users to extend/ use the source code in Cosmos to develop their version. Separation of test and source code will refine the structure but we must, also, consider easy access for a user.

What structure are you considering for this?

Refer to these projects:

It seems like the best idea to separate the "src" and "test" to each category in code folder:

In addition, the output of sorting algorithms is same, we can do this:

  • code

    • sorting

    • [src]



      • [quick_sort]


      • [quick_sort.py]


      • [quick_sort.java]


      • [merge_sort]


      • [merge_sort.cpp]



    • [test]



      • [sort.py]


      • [sort.java]



@arnavb Do you have any idea?

@iattempt, I personally like the last (and second to last) recommendation that you made, with each category having a src and test folder. I think that is the approach that should be taken.

Yes, this structure will be better to support test files which is necessary. :+1:

Ok, I will do this recently.

Solved.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

qoo2p5 picture qoo2p5  路  4Comments

rishavpandey43 picture rishavpandey43  路  3Comments

athangkanos picture athangkanos  路  4Comments

arnavb picture arnavb  路  3Comments

CaramelHeaven picture CaramelHeaven  路  3Comments