Testing & Quality Assurance (QA)

Throughout this phase, each aspect of the implementation and integration is thoroughly tested for performance, quality, and accuracy.

The testing phase is completed in a testing environment and will not affect the current day-to-day function of your team. Testing ensures everything is working as intended before we train and roll out to your team.

Team Roles:

  • Client Success Manager
  • Developer
  • Solutions Architect
  • Digital Integrations Specialist

Internal Testing

Internal testing, or the initial QA, is the process where the internal ManoByte team will go through the testing environment and comb out issues with usability. This is an overarching run-through of the processes we’ve built. During this test, the ManoByte team will:

  • Ensure the basic configuration of HubSpot and all integrations is correct
  • Ensure all workflows, automations, and dashboards have been built according to the data map
  • Bring in team members who were not involved in the initial setup to test the usability and ensure it’s logical and everything is connected

Estimated time for internal testing: 1 week

This phase can take longer if:

  • Configuration is incomplete, delaying start time

Data Quality Checking

During the strategy and data mapping phase, we planned out how data would flow between HubSpot and your other applications. Data quality checking ensures that information is being pulled from the correct places and ends up in the correct format between applications. During the data quality checking process, the developer will:

  • Test all mapped data fields with sample data
  • Ensure data is formatted correctly and landing in the right fields per the data map
  • Reconfigure and adjust integrations to resolve issues

Estimated time for data quality checking: 1 week

This phase can take longer if:

  • Data mapping is complex
  • There is a delay in receiving sample data from the client
  • The integration is custom developed

Process Testing

One significant aspect of HubSpot is the ability to create internal workflows and automation sequences. When it comes to process testing, our team will be running all of these workflows and automation to ensure they’re working and the correct roles will receive the right notifications. During the process testing process, the digital integrations specialist and solutions architect will:

  • Confirm all workflows and automation sequences are set up as defined in the data map.
  • Test all workflows and automation.
  • Reconfigure and adjust workflows and automation to resolve any issues

Estimated time for process testing: 1 week

This phase can take longer if:

  • Workflows and automation sequences are complex
  • Workarounds within HubSpot are needed to achieve specific sequences

Acceptance Testing

Once the platform has been thoroughly tested by our team, you will be able to test everything to ensure it meets expectations. You will receive access to the testing environment if you do not have it already, and key people on your team will have time to review the platform, integrations, and processes. During acceptance testing:

  • The client success manager will meet with you to walk through the platform before handing it off to you for testing
  • You and your team will be able to test everything yourselves and document any issues or concerns you find
  • Once you’ve completed your testing, our team will address your documented concerns

Estimated time for acceptance testing: 1-2 weeks

This phase can take longer if:

  • There is a delay in conducting the acceptance testing
  • Too many people are testing the platform
    • We recommend 3-5 testers
    • Involve roles like your HubSpot champion and managers in the departments using the platform.

Break / Fix Testing

Testing situations that may break the platform, adding preventive measures, and documenting fixes to cover in training.

Break/fix testing is a type of testing that anticipates unique situations or sequences that could “break” the platform and integrations, cause bad data flow, or halt workflows. While not every situation can be anticipated, break/fix testing helps catch major problems and allows us to prevent them or document fixes from addressing in training. During break/fix testing, the ManoByte team will work with you to:

  • Identify outlier situations where the platform may not work as intended
  • Test these situations to confirm how the platform “breaks”
  • Adjust the platform and integrations to prevent breaks
  • Document these situations, including fixes, to address during training

Estimated time for break/fix testing: 1-2 weeks

This phase can take longer if:

  • Remapping is required to address certain breaks

Common Issues

There are a few common issues that can extend the testing phase from the estimated timeline.

Configuration Issues

Configuring the HubSpot platform and any integrations can take longer if the ManoByte team does not receive the necessary information in a timely manner. This information can include things like:

  • Client IP addresses to exclude from tracking analytics
  • User information
  • Incorrect or delayed access to necessary applications for integration

Configuration is an extremely critical step in the implementation process. This initial configuration is the foundation for the implementation, and skipped or missing information can hold up other steps of the process or make certain tasks impossible.

Access Issues

Access issues, as mentioned above, include incorrect or delayed access to necessary platforms. Our development team will need certain access to applications to be integrated with HubSpot in order to implement or build integrations. Not receiving the correct access can halt development.

If you are unsure how to get the developer the right access, consult with your I.T. team or partner. We can also meet via Zoom to walk you through access permissions for some platforms.

Feedback Issues

There will be a few times throughout the process when we will need feedback from you, such as during the acceptance testing process. Where feedback is needed, we generally give your team a full week to test unless more time is discussed beforehand. Pushing back meetings or extending testing time prolongs the entire testing phase.