Skip to content
This repository has been archived by the owner on Sep 2, 2024. It is now read-only.

Need for 'Test_definitions' folder under 'code' #302

Closed
Kevsy opened this issue Sep 7, 2023 · 3 comments
Closed

Need for 'Test_definitions' folder under 'code' #302

Kevsy opened this issue Sep 7, 2023 · 3 comments

Comments

@Kevsy
Copy link
Contributor

Kevsy commented Sep 7, 2023

Problem description:
As discussed in #61 , there is a minimum requirement for a .feature file to satisfy the test criteria for API Readiness.

The discussion includes the point "Everyone seem to agree that .feature file in main subproject will help with compliance of minimum checklist criteria document."

It seems sensible to place this .feature file(s) in a folder under code, i.e. `/code/Test_definitions' to make it easier to find.

Reference PR

@eric-murray
Copy link
Contributor

This needs to be moved to Commonalities. I do not have the necessary permissions for this. Maybe @shilpa-padgaonkar or @rartych can oblige.

@Kevsy
Copy link
Contributor Author

Kevsy commented Sep 7, 2023

Thanks, too many repos open! Will delete this and re-open in Commonalities.

@Kevsy Kevsy closed this as completed Sep 7, 2023
@rartych
Copy link
Contributor

rartych commented Sep 7, 2023

@Kevsy Yes, we should update the subproject template repository, not only with tests placeholder, but also with Github issue templates etc.

The issue in Commonalities subproject is the right way, then my colleagues from DT can update https://github.com/camaraproject/Template_Lead_Repository - hopefully before opening new subprojects.

In case of existing repositories it should be manually keeping the folder structure decided in Commonalities.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants