FM BetterForms Docs
BF Editorfmbetterforms.com
Engineering Reference Docs
Engineering Reference Docs
  • BF Streaming Proxy
  • Updating the Helper File
  • Connection Trouble Shooting Guide
  • Software Testing - Overview
    • Types of Testing
    • UX/UI Checklist
      • Pages
        • Login 🔑
        • Pricing 💵
        • 404 🤷‍♂️
        • Contact Us ☎️
        • Sign Up 👋
        • FAQ ❓
        • Blog Post 🗞
        • Careers 💼
        • Team 👫
        • Cart 🛒
        • Press 📸
        • Search results 🔍
      • Elements
        • Avatar 😁
        • Badge 📛
        • Button 🖲️
        • Card 🃏
        • Table 📏
        • Icon 🌠
        • Text Field ⌨️
        • Toggle 🎛️
        • Loading ⏳
        • Modal 🎉
        • Tooltip 🛠
        • Search 🕵️‍♀️
        • Navigation 🧭
        • Radio 📻
        • Checkbox ☑️
        • Tabs 🗂
        • Toast 🍞
      • Flows
        • Submitting a form 📨
        • Making a payment 💳
        • Contacting support 🆘
        • Deleting account 🗑
        • Tracking progress 📈
        • Resetting password 🤫
        • Showing input error 🚨
        • Entering a promo code 🏷️
        • Saving changes 💾
        • Canceling subscription 🛑
      • Topics
        • Responsiveness 🎚
        • Typography 🔤
        • Dark mode 🌑
        • Accessibility 🚹
        • Colors 🎨
        • UX Writing ✏️
      • Brand
        • Logo 💠
        • Social Media 🔉
        • Typography 🔠
    • FM BetterForms - Quality Assurance
    • JavaScript Libraries
  • Rollbacks and Version Control
  • BF Server Proxy
  • Base code End of Life - 0.8.78-0.8111
  • Setting up Auth0
    • Introduction
    • Getting started
      • Creating a tenant
      • Creating Application
      • Additional customizations
        • Allowed Callback URLs
    • Creating a Database
      • Choosing different login options
        • Social Connections
        • Username and password (Auth0)
        • Creating new BF Users
        • Using Auth0 in an iFrame
        • Configuring FM BetterForms
        • Additional Notes
  • Create an S3 Bucket on AWS
  • ApexCharts - Getting started
  • BF Enterprise Documentation
    • Overview
      • Features
      • Overview Diagram
    • Requirements
    • Env File
    • Setting up the Server
      • Installation
      • Loading image to a local repository
      • Starting server
      • Restarting Policies
      • Scaling up
    • Hardware Recommendations
    • FM Credentials - Helper file
    • How it works
      • Development
      • Downloading environment data
  • BetterForms Error Pages API
    • Introduction
    • Dynamic Error Page
    • Static Error Page
    • Custom error pages
    • Custom error handlers
    • Error Code List
  • BF Streaming API
  • Creating a PWA
    • Introduction
    • Getting Started
      • Making it installable
      • Browser Support
      • Sending Push Notifications
      • Sending a Push Notification from the API Endpoint
      • Adding DOM Header Insertion to be Available for Offline Use
Powered by GitBook
On this page

Was this helpful?

  1. Software Testing - Overview

FM BetterForms - Quality Assurance

At Delfs' Engineering, we take pride in our quality control process, which is an integral part of our commitment to delivering exceptional products and services to our clients.

Our QA process is structured to ensure a high level of quality at every stage of project development. Here's an overview of how our QA process works:

Initial Assessment: Our team closely collaborates with the client, and the QA process begins with an initial assessment of project requirements, objectives, and client expectations.

Test Planning: Once project requirements are defined, our QA specialist creates a comprehensive test plan. This plan outlines the scope of testing, test cases, testing environments, and timelines.

Testing Execution: Our QA department conducts various types of testing, including functional, performance, security, and usability testing. Each test is designed to identify and resolve potential issues, ensuring the product meets quality standards.

Bug Tracking: Throughout the testing phase, any identified issues are meticulously tracked and documented. Our team categorizes and prioritizes these issues for resolution.

Regression Testing: Whenever code changes are made, we conduct regression testing to verify that existing functionalities remain intact and unaffected by updates.

Client Collaboration: We maintain open communication with our clients, providing regular updates on testing progress, issue resolution, and results. Client feedback is invaluable for refining our processes.

Final Verification: Before product deployment, we perform a final verification to ensure all quality standards have been met. This includes testing on various devices, browsers, and platforms to guarantee compatibility.

Documentation: Testing results and any issues encountered during testing are thoroughly documented.

Post-Deployment Support: Our commitment to quality extends beyond deployment. We provide post-deployment support to address any unforeseen issues and ensure a smooth user experience.

At Delfs' Engineering, we believe that the QA process is a fundamental element in building trust and maintaining long-term partnerships with our clients.

PreviousTypography 🔠NextJavaScript Libraries

Last updated 11 months ago

Was this helpful?