This guide will help you get started with Development Stockpile for EFSS development and testing.
Before you begin, ensure you have the following installed:
- Docker Engine (20.10.0 or higher)
- Docker Compose (2.0.0 or higher)
- Git
- At least 4GB of RAM
- 20GB of free disk space
- Internet connection for pulling Docker images
- Visual Studio Code with Docker extension
- Act for local GitHub Actions testing
- Xdebug for PHP debugging
- Clone the repository:
git clone https://github.com/pondersource/dev-stock.git
cd dev-stock
- Pull required Docker images:
./docker/pull/all.sh
- Install Node.js dependencies:
npm install
- Copy and configure environment variables:
cp .env.example .env
# Edit .env with your preferred settings
The OCM Test Suite supports various test scenarios. Before running any tests, please check our Platform Compatibility Matrix to ensure your target platforms and versions are compatible with the feature you want to test.
- Login Tests:
./dev/ocm-test-suite.sh login nextcloud v30.0.2 dev chrome
- Share Link Tests:
./dev/ocm-test-suite.sh share-link nextcloud v30.0.2 dev chrome owncloud v10.15.0
- Share With Tests:
./dev/ocm-test-suite.sh share-with nextcloud v30.0.2 dev chrome nextcloud v30.0.2
- Invite Link Tests:
./dev/ocm-test-suite.sh invite-link nextcloud-sm v27.1.11-sm ci chrome owncloud-sm v10.15.0-sm
./dev/ocm-test-suite.sh <category> <platform1> <version1> <mode> <browser> [platform2] [version2]
category
: login, share-link, share-with, or invite-linkplatform1
: nextcloud, owncloud, ocmstub, seafile, or ocisversion1
: platform version (e.g., v30.0.2)mode
: dev or cibrowser
: chrome or firefoxplatform2
: (optional) second platform for cross-platform testsversion2
: (optional) version of the second platform
dev-stock/
├── cypress/ # Test suites and configurations
├── docker/ # Docker configurations and images
│ ├── build/ # Image build scripts
│ ├── configs/ # Platform configurations
│ ├── pull/ # Image pull scripts
│ └── scripts/ # Utility scripts
├── docs/ # Documentation
├── .github/ # GitHub Actions workflows
└── dev/ # Development scripts
- Building custom images:
./docker/build/all.sh
- Cleaning previous test data and docker containers:
./scripts/clean.sh
After getting started, you might want to:
- Learn about Docker Images
- Explore the OCM Test Suite
- Set up Xdebug for debugging
- Configure GitHub Actions for CI/CD
If you encounter any issues:
- Check the logs using
docker logs <container_name>
- Review test screenshots in
cypress/screenshots
- Search existing GitHub issues
- Create a new issue with detailed reproduction steps
We welcome contributions! Please see our Contributing Guide for details.