TESTING.md

Testing 🧪

Readme navigation links: 🧭

• 📕 View Readme documentation
• 🎨 View Design documentation
• 🚀 View Deployment documentation (Local & Production)
• ✨ View Features documentation
• 🔓 View Security documentation

---

The testing documentation offers a thorough walkthrough of the website's testing procedures and functionality. It includes screenshots from various testing stages for visual guidance. This essential resource assists individuals looking to delve deeper into the testing aspects of the website. It's arranged into multiple sections, each emphasising a specific testing procedure or function. The sections included are:

• Code Validation
  • HTML
  • CSS
  • JavaScript
  • Python
• Browser Compatibility
• Responsiveness
• Lighthouse Audit
• User Story Testing
• Automated Testing
  • Python (Unit Testing)
    • Unit Test Issues
• Bugs
  • GitHub Issues
• Unfixed Bugs

Code Validation

For Code Validation, I have used the following tools: 🛠️

• W3C HTML Validator Validates HTML code
• Jigsaw CSS Validator Validates CSS code
• PEP8 CI Python Linter Validates Python code
• JShint JavaScript Validator Validates JavaScript code
• Eslint for JavaScript linting
• Ruff python linter for Python linting & formatting
• Pycharm Code Inspections for Python linting (use pep8 style guide)

HTML

I have employed the W3C Markup Validation Service, which is the recommended tool for validating all of my HTML files. The validation process ensures accuracy and adherence to industry standards. To access the validator, please visit the following URL: W3C Markup Validation Service.

Important

HTML validation info messages

I utilised the prettier formatter to properly format the HTML, which leads to the inclusion of trailing slashes at the conclusion of tags. It is important to note that while this may prompt an informational message in HTML validation reports, it does not constitute an error.

Page	W3C URL	Screenshot	Notes
About us	W3C		No warnings
Contact Us	W3C		No warnings
FAQS	W3C		No warnings
Privacy Policy	W3C		No warnings
Products	W3C		No warnings
Product Detail	W3C		No warnings
Profile Account	Validated by input		No warnings
Profile Account Delivery Information	Validated by input		Error fixed on commit: b7a681d334ea03bb01ecee84cb5f1b5faa403d9c
Profile Account Orders	Validated by input		No warnings

CSS

I have employed the CSS Jigsaw Validator, which is the recommended tool for validating all of my CSS files. The validation process ensures accuracy and adherence to industry standards. To access the validator, please visit the following URL: CSS Jigsaw Validator.

Important

CSS validation errors:

This project uses Tailwind CSS, which is a utility-first CSS framework. As such, the css is compiled & minified into one css file with Vite. CSS validation has returned 56 CSS parsing errors. This issue is a result of the final ccs build using Tailwindcss. The maintainer of TailwindCSS has discussed this issue and provided a solution; however, the recommended fix cannot be used as it is causing issues with the styles used within the application. Remove --tw- variables from universal selector #7317

File	Jigsaw URL	Screenshot	Notes
main.css Navigate to file	Jigsaw		Fail: (61) Errors. These errors are due to the --tw- variables from universal mentioned above.

JavaScript

I have used the recommended JShint Validator to validate all of my JS files along with ESLint for JavaScript linting.

If using modern JavaScript (ES6) methods, then make sure to include the following line at the very top of every single JavaScript file (this should remain in your files for submission):

Note

ESLint Configuration

/* jshint esversion: 11 */ & /* jshint asi: true */ have been added to the top of each JS file for assessment purposes. This allows the JShint validator to recognize modern ES6 methods, such as: let, const, template literals, arrow functions (=>), etc.

File	Screenshot	Notes
main.js Navigate to file		Pass: No Errors
stripe.js Navigate to file		Pass: No Errors
wishlist.js Navigate to file		Pass: No Errors
wishlist_append_to_dialog.js Navigate to file		Pass: No Errors
Build file main.js Located in ~/static/dist/ directory		Pass: No Errors
Build file stripe.js Located in ~/static/dist/ directory		Pass: No Errors
Build file wishlist.js Located in ~/static/dist/ directory		Pass: No Errors

Python

I have utilised the Ruff Python linter to validate and format all of my Python files according to the PEP8 standards. This was done in conjunction with the PyCharm IDE. Additionally, I employed the recommended PEP8 CI Python Linter to validate all files excluding diregtories in the tests & migrations folders, as well as __init__.py files.

Important

Testing Python Code

Folders excluded from testing include: tests & migrations. Files excluded from testing include: __init__.py files.

Status	Filename	Result Text
Pass	./apps/home/apps.py	All clear, no errors found
Pass	./apps/home/urls.py	All clear, no errors found
Pass	./apps/home/views.py	All clear, no errors found
Pass	./apps/ecommerce/products/models.py	All clear, no errors found
Pass	./apps/ecommerce/products/apps.py	All clear, no errors found
Pass	./apps/ecommerce/products/admin.py	All clear, no errors found
Pass	./apps/ecommerce/products/utils.py	All clear, no errors found
Pass	./apps/ecommerce/products/urls.py	All clear, no errors found
Pass	./apps/ecommerce/products/views.py	All clear, no errors found
Pass	./apps/ecommerce/checkout/signals.py	All clear, no errors found
Pass	./apps/ecommerce/checkout/apps.py	All clear, no errors found
Pass	./apps/ecommerce/checkout/webhook_handler.py	All clear, no errors found
Pass	./apps/ecommerce/checkout/webhooks.py	All clear, no errors found
Pass	./apps/ecommerce/checkout/urls.py	All clear, no errors found
Pass	./apps/ecommerce/checkout/views.py	All clear, no errors found
Pass	./apps/ecommerce/cart/apps.py	All clear, no errors found
Pass	./apps/ecommerce/cart/context_processors.py	All clear, no errors found
Pass	./apps/ecommerce/cart/urls.py	All clear, no errors found
Pass	./apps/ecommerce/cart/views.py	All clear, no errors found
Pass	./apps/ecommerce/orders/models.py	All clear, no errors found
Pass	./apps/ecommerce/orders/apps.py	All clear, no errors found
Pass	./apps/ecommerce/orders/forms.py	All clear, no errors found
Pass	./apps/ecommerce/orders/admin.py	All clear, no errors found
Pass	./apps/ecommerce/orders/tests.py	All clear, no errors found
Pass	./apps/ecommerce/orders/urls.py	All clear, no errors found
Pass	./apps/ecommerce/orders/views.py	All clear, no errors found
Pass	./apps/ecommerce/wishlist/models.py	All clear, no errors found
Pass	./apps/ecommerce/wishlist/apps.py	All clear, no errors found
Pass	./apps/ecommerce/wishlist/forms.py	All clear, no errors found
Pass	./apps/ecommerce/wishlist/urls.py	All clear, no errors found
Pass	./apps/ecommerce/wishlist/views.py	All clear, no errors found
Pass	./apps/customer_support/apps.py	All clear, no errors found
Pass	./apps/customer_support/forms.py	All clear, no errors found
Pass	./apps/customer_support/context_processors.py	All clear, no errors found
Pass	./apps/customer_support/urls.py	All clear, no errors found
Pass	./apps/customer_support/views.py	All clear, no errors found
Pass	./apps/subscriptions/models.py	All clear, no errors found
Pass	./apps/subscriptions/apps.py	All clear, no errors found
Pass	./apps/subscriptions/forms.py	All clear, no errors found
Pass	./apps/subscriptions/admin.py	All clear, no errors found
Pass	./apps/subscriptions/urls.py	All clear, no errors found
Pass	./apps/subscriptions/views.py	All clear, no errors found
Pass	./apps/accounts/signals.py	All clear, no errors found
Pass	./apps/accounts/models.py	All clear, no errors found
Pass	./apps/accounts/apps.py	All clear, no errors found
Pass	./apps/accounts/forms.py	All clear, no errors found
Pass	./apps/accounts/admin.py	All clear, no errors found
Pass	./apps/accounts/urls.py	All clear, no errors found
Pass	./apps/accounts/views.py	All clear, no errors found
Pass	./apps/marketing/models.py	All clear, no errors found
Pass	./apps/marketing/apps.py	All clear, no errors found
Pass	./apps/marketing/admin.py	All clear, no errors found

Important

Extended Python Validation screenshots and links

The following table contains links to the PEP8 CI Python Linter validation results for each file.

View detailed testing with screenshots with CI Python Linter links

Status	Filename	Screenshot	Result	CI URL
Pass	./apps/home/apps.py		All clear, no errors found	Link
Pass	./apps/home/urls.py		All clear, no errors found	Link
Pass	./apps/home/views.py		All clear, no errors found	Link
Pass	./apps/ecommerce/products/models.py		All clear, no errors found	Link
Pass	./apps/ecommerce/products/apps.py		All clear, no errors found	Link
Pass	./apps/ecommerce/products/admin.py		All clear, no errors found	Link
Pass	./apps/ecommerce/products/utils.py		All clear, no errors found	Link
Pass	./apps/ecommerce/products/urls.py		All clear, no errors found	Link
Pass	./apps/ecommerce/products/views.py		All clear, no errors found	Link
Pass	./apps/ecommerce/checkout/signals.py		All clear, no errors found	Link
Pass	./apps/ecommerce/checkout/apps.py		All clear, no errors found	Link
Pass	./apps/ecommerce/checkout/webhook_handler.py		All clear, no errors found	Link
Pass	./apps/ecommerce/checkout/webhooks.py		All clear, no errors found	Link
Pass	./apps/ecommerce/checkout/urls.py		All clear, no errors found	Link
Pass	./apps/ecommerce/checkout/views.py		All clear, no errors found	Link
Pass	./apps/ecommerce/cart/apps.py		All clear, no errors found	Link
Pass	./apps/ecommerce/cart/context_processors.py		All clear, no errors found	Link
Pass	./apps/ecommerce/cart/urls.py		All clear, no errors found	Link
Pass	./apps/ecommerce/cart/views.py		All clear, no errors found	Link
Pass	./apps/ecommerce/orders/models.py		All clear, no errors found	Link
Pass	./apps/ecommerce/orders/apps.py		All clear, no errors found	Link
Pass	./apps/ecommerce/orders/forms.py		All clear, no errors found	Link
Pass	./apps/ecommerce/orders/admin.py		All clear, no errors found	Link
Pass	./apps/ecommerce/orders/tests.py		All clear, no errors found	Link
Pass	./apps/ecommerce/orders/urls.py		All clear, no errors found	Link
Pass	./apps/ecommerce/orders/views.py		All clear, no errors found	Link
Pass	./apps/ecommerce/wishlist/models.py		All clear, no errors found	Link
Pass	./apps/ecommerce/wishlist/apps.py		All clear, no errors found	Link
Pass	./apps/ecommerce/wishlist/forms.py		All clear, no errors found	Link
Pass	./apps/ecommerce/wishlist/urls.py		All clear, no errors found	Link
Pass	./apps/ecommerce/wishlist/views.py		All clear, no errors found	Link
Pass	./apps/customer_support/apps.py		All clear, no errors found	Link
Pass	./apps/customer_support/forms.py		All clear, no errors found	Link
Pass	./apps/customer_support/context_processors.py		All clear, no errors found	Link
Pass	./apps/customer_support/urls.py		All clear, no errors found	Link
Pass	./apps/customer_support/views.py		All clear, no errors found	Link
Pass	./apps/subscriptions/models.py		All clear, no errors found	Link
Pass	./apps/subscriptions/apps.py		All clear, no errors found	Link
Pass	./apps/subscriptions/forms.py		All clear, no errors found	Link
Pass	./apps/subscriptions/admin.py		All clear, no errors found	Link
Pass	./apps/subscriptions/urls.py		All clear, no errors found	Link
Pass	./apps/subscriptions/views.py		All clear, no errors found	Link
Pass	./apps/accounts/signals.py		All clear, no errors found	Link
Pass	./apps/accounts/models.py		All clear, no errors found	Link
Pass	./apps/accounts/apps.py		All clear, no errors found	Link
Pass	./apps/accounts/forms.py		All clear, no errors found	Link
Pass	./apps/accounts/admin.py		All clear, no errors found	Link
Pass	./apps/accounts/urls.py		All clear, no errors found	Link
Pass	./apps/accounts/views.py		All clear, no errors found	Link
Pass	./apps/marketing/models.py		All clear, no errors found	Link
Pass	./apps/marketing/apps.py		All clear, no errors found	Link
Pass	./apps/marketing/admin.py		All clear, no errors found	Link

---

Important

Django settings.py

The Django settings.py file comes with 4 lines that are quite long, and will throw the E501 line too long error. This is default behavior, but can be fixed by adding # noqa to the end of those lines.

AUTH_PASSWORD_VALIDATORS = [
    {
        "NAME": "django.contrib.auth.password_validation.UserAttributeSimilarityValidator",  # noqa
    },
    {
        "NAME": "django.contrib.auth.password_validation.MinimumLengthValidator",  # noqa
    },
    {
        "NAME": "django.contrib.auth.password_validation.CommonPasswordValidator",  # noqa
    },
    {
        "NAME": "django.contrib.auth.password_validation.NumericPasswordValidator",  # noqa
    },
]

Browser Compatibility

Note

Browser Screenshots

Screenshots of the deployed project on various browsers can be found in the docs/testing/browser-testing directory. Due to the large number of screenshots, the browsers have been categorized based on their types and can be accessed in the dropdown menu below view detailed screenshots. Nearly all pages have been tested on mobile & desktop in Chrome, Firefox & Safari.

I have tested my deployed project on multiple browsers to check for compatibility issues. The browsers tested were:

• Chrome Version 121.0.6115.2 (Official Build) dev (arm64)

View detailed screenshots for Chrome

Page	Device (mobile)	Device (desktop)	Notes
About			Works as expected
Account New User Verify			Works as expected
Account Profile			Works as expected
Account Profile Delivery Information			Works as expected
Account Profile Orders No Auth			Works as expected
Cart Preview	NA		Works as expected
Checkout			Works as expected
Contact			Works as expected
FAQS			Works as expected
Home			Works as expected
Home Menu Open			Works as expected
Order Confirmation			Works as expected
Privacy			Works as expected
Product To Wishlist			Works as expected
Products			Works as expected
Products Detailed			Works as expected
Register			Works as expected
Register Confirmation Email		NA	Works as expected
Shipping & Information			Works as expected
Shopping Cart			Works as expected
Subscription Email		NA	Works as expected
Subscription Complete			Works as expected
Terms & Conditions			Works as expected
wishlist			Works as expected
wishlist Create			Works as expected
wishlist Delete			Works as expected
wishlist Edit			Works as expected
404 Not Found			Works as expected

• Firefox (Developer Edition) Version 121.056 (64-bit)

View detailed screenshots for Firefox

Browser	Device (mobile)	Device (desktop)	Notes
About			Works as expected
Account Profile			Works as expected
Account Profile Delivery Information			Works as expected
Account Profile Past Orders			Works as expected
Cart Preview	NA		Works as expected
Checkout			Works as expected
Contact			Works as expected
FAQS			Works as expected
Home			Works as expected
Home Menu Open			Works as expected
Login			Works as expected
Order Complete			Works as expected
Order Summary			Works as expected
Privacy			Works as expected
Product Add To Wishlist			Works as expected
Products All			Works as expected
Register			Works as expected
Shipping Information			Works as expected
Shopping Cart			Works as expected
Subscription Complete			Works as expected
Terms & Conditions			Works as expected
Wishlist			Works as expected
Wishlist Edit			Works as expected
Wishlist Create			Works as expected
Wishlist Delete			Works as expected
404 Not Found			Works as expected

• Safari Version 17.1 (19616.2.9.11.7)

View detailed screenshots for Safari

Browser	Device (mobile)	Device (desktop)	Notes
About			Works as expected
Account Profile			Works as expected
Account Profile Delivery Information			Works as expected
Account Profile Past Orders			Works as expected
Checkout			Works as expected
Contact			Works as expected
FAQS			Works as expected
Home			Works as expected
Home Menu Open			Works as expected
Home Subscription Signup			Works as expected
Login			Works as expected
Order Complete			Works as expected
Privacy Policy			Works as expected
Products			Works as expected
Product Detail			Works as expected
Product Detail Wishlist			Works as expected
Product Search			Works as expected
Register			Works as expected
Shipping & Information			Works as expected
Shopping Cart			Works as expected
Terms & Conditions			Works as expected
Wishlist			Works as expected
Wishlist Create			Works as expected
Wishlist Edit			Works as expected
wishlist Delete			Works as expected
404			Works as expected

Responsiveness

Device testing was conducted using the Polypane browser app, which allows for testing on multiple devices simultaneously.

The three sizes tested were:

• Mobile (320px)
• Tablet (500px)
• Desktop (12580px)

Page	Screenshots	Notes
About us		Works as expected
Cart		Works as expected
Checkout		Works as expected
Delivery Information		Works as expected
Desktop Menu		Works as expected
Email Verification		Works as expected
Home		Works as expected
Login		Works as expected
Mobile Menu		Works as expected
Products All		Works as expected
Product Detail		Works as expected
Profile		Works as expected
Profile Orders		Works as expected
Register New User		Works as expected
Register New User		Works as expected

Lighthouse Audit

Important

Lighthouse Audit The primary cause of performance issues can be attributed to the Stripe.js file and the static files obtained from the AWS S3 bucket. The Stripe.js file is essential for enabling Stripe payment functionality, while the static files from AWS are necessary for the proper functioning of CSS, JavaScript, and image files.

I have conducted a series of Lighthouse Audits on my application. The Lighthouse Audit is a tool that is built into the Chrome DevTools. It is used to measure the performance, accessibility, best practices and SEO of a website.

Note

The Lighthouse Audit was conducted on the following pages: Screenshots of the Lighthouse Audit results can be found in the docs/testing/lighthouse directory.

• About us
• Cart
• Contact us
• FAQS
• Home
• Products
• Product Detail
• Profile
• Profile Delivery Information
• Profile Orders
• Privacy Policy
• Register
• Sign In
• Terms and Conditions
• Wishlist

Page	Device (Mobile)	Device (Desktop)	Notes
About us			Minor issues
Cart			Minor issues
Contact us			Minor issues
FAQS			Minor issues
Home			Minor issues
Products			Minor issues
Product Detail			Minor issues
Profile			Minor issues
Profile Delivery Information			Minor issues
Profile Orders			Minor issues
Privacy Policy			Minor issues
Register			Minor issues
Sign In			Minor issues
Terms and Conditions			Minor issues
Wishlist			Minor issues

User Story Testing

During the development of the Elite Fitness website, I utilised User Story Testing. This approach placed emphasis on the end user's perspective, ensuring that the website's development and validation corresponded with practical, real-world requirements.

I categorised the user stories into three segments: • New Customers • Returning Customers • Site Administrators

This categorisation provides a comprehensive overview of each accomplished user story. Each story is presented with the following structure:

1. The User Story: This describes the specific task or functionality from the perspective of the end user.
2. Requirement Met: Here, I state whether the proposed functionality or attribute has been successfully implemented.
3. Screenshot: Visual proof of the implemented attribute or functionality is provided through a screenshot.

This structure ensures a systematic and user-centred approach to our website development process.

User stories for new customers

User Story (new customers)	Requirement met	Screenshot
As a new site user, I would like to View the website on both mobile and desktop devices, so that I can access the site conveniently.	✅
As a new site user, I would like to Easily navigate throughout the site, so that I can find products or information I may need.	✅
As a new site user, I would like to Contact customer service, so that I can obtain assistance regarding product inquiries or general questions I may have.	✅
As a new site user, I would like to search for products available, so that I can locate and explore the range of available products.	✅
As a new site user, I would like to filter through available products, so that I can easily view & find products quickly.	✅
As a new site user, I would like to view detailed information on the product, so that I can make an informed purchase decision.	✅
As a new site user, I would like to add my products to my shopping cart, so that I can easily make my purchase.	✅
As a new site user, I would like to preview my shopping cart, so that I can see what items I have added to my cart & quickly view the total cost of goods.	✅
As a new site user, I would like to view the shipping information, so that I can gain a comprehensive understanding of the shipping policies prior to finalising any purchase..	✅
As a new site user, I would like to signup to the newsletter, so that I can avail of exclusive offers and receive information on fitness & wellness.	✅
As a new site user, I would like to modify the items within my shopping cart, so that I can adjust quantities or eliminate products from my cart as needed.	✅
As a new site user, I would like to review the products and their associated costs prior to making a final purchase, so that I can validate my intended purchases and ensure their accuracy before proceeding with the payment.	✅
As a new site user, I would like to receiving a comprehensive summary of my recent purchase, so that I can the details of my purchases accurately.	✅
As a new site user, I would like to an email confirmation of my purchase, so that I can verify the successful completion of my transaction.	✅
As a new site user, I would like to create an account, so that I can access and modify my personal information, as well as review my previous transactions.	✅
As a new site user, I would like to receive confirmation email upon registration, so that I can authenticate my account sign-up.	✅

User stories for returning customers

User Story (returning customers)	Requirement met	Screenshot
As a returning site user, I would like to log in to my account, so that I can access my personal information and review my previous orders.	✅
As a returning site user, I would like to reset my password, so that I can in the event that I have forgotten it.	✅
As a returning site user, I would like to receive feedback upon submitting my email for the purpose of resetting my password, so that I can be assured I have entered the correct email address.	✅
As a returning site user, I would like to access my account, so that I can review and modify my account information.	✅
As a returning site user, I would like to access my account, so that I can review and modify my delivery details.	✅
As a returning site user, I would like to receive confirmation whenever there are updates made to my account details, so that I can be assured my information has been successfully updated.	✅
As a returning site user, I would like to access my account, so that I can review my previous orders. ✅
As a returning site user, I would like to create a wishlist, so that I can add products for potential future purchase.	✅
As a returning site user, I would like to add product easily to a wishlist, so that I can promptly transfer them to my shopping cart.	✅
As a returning site user, I would like to modify my wishlist, so that I can rename my wishlist or add a description.	✅
As a returning site user, I would like to create a wishlist, so that I can compile a collection of products that I may consider purchasing at a later time..	✅
As a returning site user, I would like to confirmation message regarding the update of my wishlist, so that I can hat the changes have been successfully implemented.	✅
As a returning site user, I would like to easily navigate to my wishlists, so that I can conveniently review the products I have previously added to my wishlists..	✅

User stories for site administrators

User Story (site administrators)	Requirement met	Screenshot
As a site administrator, I should be able to modify customer delivery information, so that I can make any necessary changes needed.	✅
As a site administrator, I should be able to access and review customer orders, so that I can efficiently evaluate both the orders themselves and their details.	✅
As a site administrator, I should be able to edit customer orders, so that I can qmake any necessary changes needed.	✅
As a site administrator, I should be able to modify product attributes, so that I can make changes to product attributes.	✅
As a site administrator, I should be able to modify product categories, so that I can make changes to product categories.	✅
As a site administrator, I should be able to modify products, so that I can make changes to the available products.	✅
As a site administrator, I should be able to have a overview of available products, so that I can examine stock quantities, prices, and the most recent update of each product..	✅
As a site administrator, I should be able to modify customer subscriptions, so that I can update subscriber information or remove subscribers if necessary..	✅

Automated Testing

I have conducted a series of automated tests on my application.

I fully acknowledge and understand that, in a real-world scenario, an extensive set of additional tests would be more comprehensive.

Python (Unit Testing)

I have used Django's built-in unit testing framework to test the application functionality.

In order to run the tests, I ran the following command in the terminal each time:

python3 manage.py test name-of-app

To create the coverage report, I would then run the following commands:

coverage run --source=name-of-app manage.py test

coverage report

To see the HTML version of the reports, and find out whether some pieces of code were missing, I ran the following commands:

coverage html

python3 -m http.server

Accounts App

App	File	Coverage	Screenshot
Total Coverage		99%
Accounts	apps/accounts/apps.py	100%
Accounts	apps/accounts/admin.py	100%
Accounts	apps/accounts/forms.py	100%
Accounts	apps/accounts/models.py	100%
Accounts	apps/accounts/urls.py	100%
Accounts	apps/accounts/views.py	95%
Accounts	apps/accounts/signals.py	82%

Checkout App

App	File	Coverage	Screenshot
Total Coverage		100%
Customer Support	apps/customer_support/apps.py	100%
Customer Support	apps/customer_support/context_processors.py	100%
Customer Support	apps/customer_support/forms.py	100%
Customer Support	apps/customer_support/views.py	100%

Ecommerce App

App	File	Coverage	Screenshot
Total Coverage		79%
Cart	apps/ecommerce/cart/apps.py	100%
Cart	apps/ecommerce/cart/context_processors.py	73%
Cart	apps/ecommerce/cart/urls.py	100%
Cart	apps/ecommerce/cart/views.py	82%

Products App

App	File	Coverage	Screenshot
Total Coverage		88%
Products	apps/ecommerce/products/admin.py	85%
Products	apps/ecommerce/products/apps.py	100%
Products	apps/ecommerce/products/models.py	88%
Products	apps/ecommerce/products/urls.py	100%
Products	apps/ecommerce/products/utils.py	100%
Products	apps/ecommerce/products/views.py	80%

Unit Test Issues

Important

Unit Test Issues Apart from the previously mentioned Django tests, I have formulated a series of unit tests for diverse applications. Unfortunately, due to project-imposed time constraints, I was unable to generate unit tests for all applications.

Bugs 🐛

To the best of my knowledge, there are no bugs present in my application.

🔝 Back to Top