CKAN Integration Test/Benchmark Suite #6424
jqnatividad
started this conversation in
Ideas
Replies: 1 comment
-
We already have cypress as testing tool for JavaScript code, I've been planning to extend its use to actual front-end testing, just need to design how to populate data in consistent and fast manner for tests. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
It would be nice if CKAN had a standard integration test/benchmark suite. With it, we can:
as we discuss unit test approach (Rethinking CKAN's Unit Test approach. #6373), a benchmark suite can also serve as an integration test, and could be made part of the release checklist.
with the recent Python 3/Flask migration effort largely done for CKAN core, the pace of contributions has increased and it would be nice to have an objective way to measure the impact of architectural choices as we continue to modernize the platform.
Also, because of the highly extensible nature of CKAN, it will be a good tool to objectively measure and isolate undesired side effects of extensions.
Various test types come to mind:
Using the standard templates, test with a tool like Selenium
Using a tool like Postman not only helps with API Testing, it can make the API more accessible to downstream API users and extension developers as Postman is also widely used by developers.
Beta Was this translation helpful? Give feedback.
All reactions