Dynamics 365 Trial

Quality Assurance

Devide Line

Software engineering service for the development of custom CRM

Service Dropdown

Software Quality Assurance (SQA) is the systematic approach towards meeting the predefined and standard quality specifications on the client requirements using relevant testing methodologies. The objective of software quality assurance is to deliver a high-quality software.

MTC’s Guaranteed Software Quality Assurance Model (GSQAM) is step beyond SQA in which it leverages its homegrown enterprise grade software product “TotalServ Pro” to build automated testing pieces in a phased manner that gets triggered based on the predefined conditions set by the users. As a result, every piece of software developed is being tested thoroughly using modern testing methodologies in the least time possible with limited human intervention.

MTC’s GSQAM COMPRISES OF 4 POWERFUL COMPONENTS AS LISTED BELOW

Requirements Management

1. Good Requirements Management

All client requirements are analyzed and templated with actual forecast information. A 100% client requirements is mapped in TotalServ Pro (TSP) with clear depiction of forecast information using Project Gantt. Single click proposals are embedded and sent in personalized email templates which are viewable at customer’s end with TSP Online Customer Portal.

2. Good QA Process From The Beginning

TSP Gantt Templates trigger automatic quality testing workflows for any given job/job task(s) ensuring Quality Assurance right from the beginning.

3. Elaborate Testing Types for Best Quality Assurance

All testing types including unit test, integration test, performance test and regression test are conducted at regular intervals for best quality assurance.

4. Continuous Feedback Loop Built-in

MTC’s Trilogy of Feed Back Quality Assurance include:

Feedback
  1. System Anomaly Reporting
  2. Resource in-process Feed Back
  3. Customer Real-time In-process at Milestone Survey Feedback

MTC’s wide experience in quality assurance projects has worked to its advantage in publishing the most of Dynamics 365/CRM add-ons in Microsoft AppSource where each of its product code is tested and certified by Microsoft before clearing for publishing on Microsoft AppSource.

MTC’s strength in software quality assurance extends beyond product development into client services where using TotalServ Pro (TSP) each requirement – small or big is divided into job tasks and an automated testing workflow is triggered based on set quality criteria. The overall impact of its GSQAM is far-reaching with improved ROI.

MTC’s engagement policies, business philosophy, and operation control systems all revolve around a model oy transparency internally and externally.

Survey From

Several internal systems and a unique MTC culture maintain a continuous process improvement methodology and staff development program. Real-time end-to-end operational data sharing between MTC and clients, through MTC’s online portal access, assures compliance with the highest client-specific requirements while exceeding industry standard quality levels consistently.

MTC’s Step-by-Step Quality Assurance Plan - Read more

MTC is committed to deliver utmost quality in its deliverables by leveraging unique, state-of-the-art software testing methodologies.The complete testing methodology has been defined taking into several factors that are discussed in detail below.

Leveraging MTC’s GSQAM is Easy and Affordable!

MTC’s Typical Code Tests Follow Industry Best Practices

Unit Testing Plug-ins & Workflows:

Writing Testable Code Plug-ins & Workflows

  1. Unit Tests
  2. Integration Tests
  3. Debugging (Added Benefit)

Unit Testing Plug-ins & Workflows:

  1. Still Unit Test Individual Functions
  2. Use A Mocking Framework To Create IServiceProvider
  3. Can Include Pre/Post Images & Configurations
  4. No Alterations To CRM Code Required

Writing Testable Code:

  1. Small Functions With 1 Purpose
    • Separate out CRM interactions
  2. Don’t Repeat Yourself (DRY)
    • Avoid writing the same code multiple times
  3. Use Dependency Injection
    • Pass function’s required objects as parameters

Unit vs. Integration Tests:

  1. Unit Tests
    • Tests small pieces or “units” of code
    • Totally decoupled from CRM or other systems
  2. Integration Tests
    • Testing multiple parts as a group
    • Testing against dependent systems

Integration Testing Plug-ins & Workflows:

  1. Substitute Live CRM Connection In IServiceProvider Mock
  2. Use Class/Test Initialize & Cleanup Methods To Create/Delete Testing Records
  3. No Alterations To CRM Code Required

CRM and Coded UI Testing:

  1. Overview of the Coded UI Testing capabilities
  2. Test the user interface
  3. Review generated code that replicate actions

Coded UI Testing:

  1. Unit Test that interacts with the User Interface
    • Allows to find controls, inspect control properties and interact with controlse
  2. Used for Functional Testing
  3. Coded UI test are just code
    • Creates a new project and generates C# classes

Debugging:

  1. Debug Tests
    • Set breakpoints and step through the code
  2. Integrations Tests
    • Target existing CRM record(s)
    • Avoid using the plug-in profiler or console applications
GSQAM Benefits