Testing happens on both sides. We test the build against technical standards. You test it against how your business actually works.
What Zylax tests
- Browsers. Current versions of Chrome, Safari, Firefox and Edge.
- Devices. Desktop, tablet and mobile layouts, with a focus on mobile since that is where most Malaysian traffic sits.
- Forms. Submission, validation, and delivery of notification emails.
- Links and navigation. Internal links, menus and redirects from old page addresses where a site is being replaced.
- Payments and integrations. Test transactions where a gateway is involved, including declined and cancelled paths.
- Performance. Image compression, page weight and load speed.
- Search basics. Page titles, descriptions, headings, sitemap and indexing settings.
- Security. SSL, admin access and standard hardening.
What you should test
Your test is about correctness and process, not code:
- Are prices, product details, addresses, phone numbers and staff names accurate?
- Does an enquiry arrive in the right inbox, formatted so your team can act on it?
- Does an order produce the records your operations team needs?
- Does the wording say what your business actually wants to say?
- Does it read well on the phone you use every day?
How to report an issue
On the project discussion at crm.zylax.com.my, with the page address, what you did, what happened, what you expected, and a screenshot. Include your browser and device.
Bug or change request
Something not working as specified is a bug and is fixed at no cost. Something working as specified but which you now want different is a change request and is quoted. We will say which category an item falls into and why.
Test mode
Payment gateways stay in test mode until launch. Do not use a real card on staging.
To report anything found during testing, use your project thread or write to [email protected].
