In this unit, we'll cover a few common issues that can come up when building your content, as well as some steps that can be taken for possible resolution.
Before publishing to the Production Environment, it is critical to run a Quality Assurance (QA) test to make sure that everything is working properly.
Watch the video to explore the Quality Assurance (QA) Process.
Key Takeaways |
---|
Before publishing to the Production Environment, it is critical to run a Quality Assurance (QA) test to make sure that everything is working properly. We recommend having an individual other than the content builder perform the QA test. When testing, the tester should try to get into the frame of mind of a new user who is unfamiliar with the site. The tester should aim to replicate common user behavior and ensure that WalkMe provides clarity and guides the user through necessary tasks or queries with ease and efficiency. In addition to finding flaws in WalkMe content, the tester should feel free to suggest any ideas that might add value. |

Quality Assurance is an important stage in a WalkMe implementation. Quality Assurance helps ensure:
Smart Walk-Thrus play properly from beginning to end without stopping in the middle.
WalkMe items are consistent in appearance and content.
WalkMe works consistently across all desired browsers.
Relevant WalkMe Items are visible to their target audiences.

To ensure the quality of your WalkMe content before publishing, follow these steps for Quality Assurance (QA) testing:
Full Round QA is a comprehensive testing process that involves several critical checks to ensure the proper functioning of our content. It includes testing every WalkMe App from start to finish to ensure they play smoothly without any interruptions.
The text is also reviewed to ensure it is clear, concise, and free of spelling or grammatical errors. Lastly, it is important to do Crash Testing, in which we attempt to identify common missteps our end users might take. This ensures that when a user doesn't follow our content perfectly, we have a couple ways to mitigate errors and allow the content to flow appropriately.
The Sanity Check process involves performing a final run-through of our contenton various browsers and screen sizes. During this process, it is important to ensure that all elements, including Launchers and SmartTips, appear correctly and function as intended.
It is also crucial to check that all related items are Published and that tasks are completed and tracked correctly.
The figure shows some common questions to ask during the Quality Assurance process to determine if we are experiencing flow or layout issues.

Now that we're a little bit more familiar with the basics of Quality Assurance (QA), let's look at one of our main troubleshooting tools: The Flow Tracker.