Testing Backlog
Claudiu Lodromanean edited this page Apr 13, 2017
·
2 revisions
This page documents unit and end-to-end tests that need to be written to prevent regression of fixed issues or correct functionality. Feel free to submit a PR with implementations for any of these.
End-to-end Tests needed:
- A test to reproduce this issue and verify it doesn't happen again.
- A test to go through the various Default Customer Locations and verify the site is working with each one to prevent regression of this issue.
Unit Tests needed:
- TODO: Investigate code coverage and resolved issues to see what's needed.
WooCommerce is an open source commerce platform built for WordPress and lovingly crafted by Automattic and the WooCommerce community 💜. Come and work with us!
Contribution
- Set up development environment
- Our Git Flow
- SCSS and JS minification
- Naming conventions
- CSS SASS coding guidelines and naming conventions
- Critical Flows
- API Critical Flows
- String localisation guidelines
- Translating WooCommerce
- Deprecation in core
- Adding Actions and Filters
- Common Issues
- Writing high-quality testing instructions
Release Notes
- Release Testing Instructions
- 3.6.x notes/FAQ
- 2.6.x to 3.0.0 Developer Migration Notes
- Select2 fields not working in 3.0.x
- Thumbnail Image Regeneration in 3.3+
- Customizing image sizes in 3.3+
REST API and CLI
CRUD & Data Descriptions
- Database Description
- CRUD Objects in 3.0
- Order and Order Line Item Data
- Coupon Data
- Customer Data
- Product Data
- Data Stores
Internal APIs
Theming
- Enabling product gallery features (zoom, swipe, lightbox)
- Template File Guidelines for Devs and Theme Authors
Examples / Guides