Improve testing structure
See original GitHub issueTo start improving our test setup we want to bring the folder structure in line with common practices:
__tests__/{integration,helpers,...}
src
In other words __tests__
should be at the root not inside src
. The current long running test should go under test/integration
as it depends on the runtime dependencies.
This opens up the possibility to create a new folder structure that mirrors the folders under src
with 1 file per file in the production code for unit testing.
All tasks and build steps that depends on the current folder structure will need reviewing and adapting.
This was discussed as a first step to improve the testing with @dolcalmi.
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
11 Ways to Improve Software Testing through Planning, Work ...
Learn the ways to improve software testing and quality assurance through planning, establishing a productive work environment, ...
Read more >5 Ways to Improve Software Testing on Your Projects
Review of test fundamentals (such as requirements, architecture, design, interfaces) · Identify test conditions or test requirements and required ...
Read more >7 Ways to Improve the Quality of Software Testing and Hit ...
Three pillars are there to help you build effective testing strategies: test plan ; A test plan ; A test strategy ; A...
Read more >6 Ideas for Continuous Improvement in Software Testing
Are you taking the right steps for software quality improvement? Here's a checklist of QA testing best practices to help you build flawless...
Read more >How to Increase Test Efficiency in Software Testing - TestQuality
Successful software teams are continuously searching for methods to improve the efficiency of its members. They recognize that enhancing the ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
yup ok. this would also simplify what needs to be in the production docker image. right now we have an ugly script to delete the tests folders: https://github.com/GaloyMoney/galoy/blob/9f4c4ebdcb186664f500ea5420218e3b2b38d047/Dockerfile#L13
oups yeah you’re right! nevermind my comment above.