oarepo / invenio-integration-tests

Repository for testing Invenio builds

CESNET, UCT Prague and NTK wrapper around invenio v3

This meta-package contains a curated and tested set of dependencies on Invenio and OArepo libraries. It should be considered as a base building block for creating any OA repository applications.

The package contains the following dependency bundles:

Bundle name	Description
deploy	All the dependencies needed for a basic repository deployment
deploy-es7	All the ElasticSearch 7 compatible dependencies needed for a basic repository deployment
openid	Dependencies needed for openid authentication
multisum	Support for multiple file checksums (deprecated)
files	Support for uploading files
acls	ACLs support
links	Enable linking to another records
models	Includes all the common data models (DCObject, multilingual fields, Invenio model,...)
includes	Adds support to compose ES mappings by including another mappings
taxonomies	Adds support for taxonomic trees
tests	Includes test dependencies
draft	Adds support for draft records
iiif	Adds support for file (image) preview generation
micro-api	A WSGI app to serve API-only apps under the /api prefix

They could be installed, depending on needs of each repository application, by running:

pip install oarepo[bundle-name]

invenio-integration-tests's Issues

Implement integration tests for Invenio

Prepare Travis tests for lastest versions of pure Invenio (>=3.2):

• The build & tests should be tried in the following environment:

  • Python 3.8
  • PostgreSQL 9.6
  • ElasticSearch 7

• For now, it is sufficient to test the build by running something inside invenio shell

• Tests should be in a separate shell script run_tests.sh, called from travis manifest

• When the test succeeds, Travis should generate a requirements.txt artifact from pip freeze

Integrations tests do not handle all cases - for example, pytest-invenio compatibility

We should rework them to include:

• Running an API server and testing REST CRUD
• Running a UI server and testing homepage, listing and record detail
• Running a testsuite with pytest-invenio and simple service-based record crud

Only when all three are ok, release oarepo

Till this is done, oarepo building was paused so that forced sqlalchemy continuum version 1.3.15 is not overriden.

Add rest layer to integration tests

Specifically, invenio-records-rest

Reconfigure dependabot to watch correct branches

Currently dependabot reports alerts and creates PRs against the main branch, which is not used by any apps.

Can we reconfigure it to track v11 and v12 branches?