You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The common convention (good practice) is to add the term ''Test'' or ''test'' in the path or file name for the test cod.
Since it makes other readers easier to understand what source files are production code or test code.
Your way of naming test files is difficult for others to understand which are test files and it feels like mixing test code with production code.
It is a bad code organization. Thanks.
The text was updated successfully, but these errors were encountered:
Hi!
We notice that your way of naming test files doesn't follow the common naming convention.
For example, a test file is named ''https://github.com/pentaho/pentaho-platform/blob/master/repository/src/it/java/com/pentaho/pdi/ws/RepositorySyncWebServiceIT.java''
The common convention (good practice) is to add the term ''Test'' or ''test'' in the path or file name for the test cod.
Since it makes other readers easier to understand what source files are production code or test code.
Your way of naming test files is difficult for others to understand which are test files and it feels like mixing test code with production code.
It is a bad code organization. Thanks.
The text was updated successfully, but these errors were encountered: