Gitiles
Code Review Sign In
git.clicks.codes / Clicks / Forks / ERPNext / 3fa0a46f39f7024c5d0b235a7725eaa9ad0f3869
commit3fa0a46f39f7024c5d0b235a7725eaa9ad0f3869[log] [tgz]
authormarination <maricadsouza221197@gmail.com>Thu Jun 09 16:22:00 2022 +0530
committermarination <maricadsouza221197@gmail.com>Thu Jun 09 16:27:51 2022 +0530
tree338bda2ef8373b2227fe92761a83b9647d862e11
parenta6edce23977d87182b56c9b065f38f862366d1fa [diff]
chore: Less hacky tests, versioning (replace bom) and clearing log data (update cost)

- Remove `auto_commit_on_many_writes` in `update_cost_in_level()` as commits happen every N BOMs
- Auto commit every 50 BOMs
- test: Remove hacky `frappe.flags.in_test` returns
- test: Enqueue `now` if in tests (for update cost and replace bom)
- Replace BOM: Copy bom object to `_doc_before_save` so that version.py finds a difference between the two
- Replace BOM: Add reference to version
- Update Cost: Unset `processed_boms` if Log is completed (useless after completion)
- test: `update_cost_in_all_boms_in_test` works close to actual prod implementation (only call Cron job manually)
- Test: use `enqueue_replace_bom`  so that test works closest to production behaviour

Co-authored-by: Ankush Menat <ankushmenat@gmail.com>
4 files changed
tree: 338bda2ef8373b2227fe92761a83b9647d862e11
  1. .github/
  2. erpnext/
  3. .editorconfig
  4. .eslintrc
  5. .flake8
  6. .git-blame-ignore-revs
  7. .gitignore
  8. .mergify.yml
  9. .pre-commit-config.yaml
  10. .releaserc
  11. attributions.md
  12. CODE_OF_CONDUCT.md
  13. codecov.yml
  14. CODEOWNERS
  15. dev-requirements.txt
  16. license.txt
  17. package.json
  18. pyproject.toml
  19. README.md
  20. requirements.txt
  21. SECURITY.md
  22. setup.py
  23. sider.yml
  24. sponsors.md
  25. TRADEMARK_POLICY.md
  26. yarn.lock
README.md

CI UI Open Source Helpers codecov docker pulls

https://erpnext.com

ERPNext as a monolith includes the following areas for managing businesses:

  1. Accounting
  2. Warehouse Management
  3. CRM
  4. Sales
  5. Purchase
  6. HRMS
  7. Project Management
  8. Support
  9. Asset Management
  10. Quality Management
  11. Manufacturing
  12. Website Management
  13. Customize ERPNext
  14. And More

ERPNext is built on the Frappe Framework, a full-stack web app framework built with Python & JavaScript.

Installation

Login for the PWD site: (username: Administrator, password: admin)

Containerized Installation

Use docker to deploy ERPNext in production or for development of Frappe apps. See https://github.com/frappe/frappe_docker for more details.

Manual Install

The Easy Way: our install script for bench will install all dependencies (e.g. MariaDB). See https://github.com/frappe/bench for more details.

New passwords will be created for the ERPNext "Administrator" user, the MariaDB root user, and the frappe user (the script displays the passwords and saves them to ~/frappe_passwords.txt).

Learning and community

  1. Frappe School - Learn Frappe Framework and ERPNext from the various courses by the maintainers or from the community.
  2. Official documentation - Extensive documentation for ERPNext.
  3. Discussion Forum - Engage with community of ERPNext users and service providers.
  4. Telegram Group - Get instant help from huge community of users.

Contributing

  1. Issue Guidelines
  2. Report Security Vulnerabilities
  3. Pull Request Requirements
  4. Translations

License

GNU/General Public License (see license.txt)

The ERPNext code is licensed as GNU General Public License (v3) and the Documentation is licensed as Creative Commons (CC-BY-SA-3.0) and the copyright is owned by Frappe Technologies Pvt Ltd (Frappe) and Contributors.

Logo and Trademark Policy

Please read our Logo and Trademark Policy.