Both reports are accurate. What you're seeing is a function of what is being queried (and apparently that the dnsmadeeasy.com name servers have bad A records for those listed MX servers).
From the Mail Server Test Center, you're looking for the *MX* records associated with a domain. Querying 'hostmaster@williamsmoving.com' returns the eight mail servers with listed MX records (mx11 thru mx14 and mx21 thru mx24), which belong to the exchange.telus.com domain. I'm not entirely certain how the MX Dashboard retrieves the IP Addresses for those eight MX records, but doing reverse lookups on the eight IP Addresses confirms that they are correct (as relates to reverse lookups). If I do a set type=MX query from 'nslookup', I get the correct IP Addresses for the eight MX servers. My assumption would be that the MX Dashboard uses essentially the same function as 'nslookup'. The unknown answer is where did it get the valid IP Addresses from.
On the DNS Report tool, though, a complete inquiry on the entire domain is performed. One of the things that is identified is six IPv4 DNS servers and two IPv6 DNS servers at dnsmadeeasy.com (ns10 thru ns15). An 'SOA' query on the domain confirms this information. This is where the problem seems to surface. If you query any one of those six name servers servers directly, they return the same IP Address for all eight MX records, which is 54.235.159.97. A reverse lookup on that IP Address identifies it as an Amazon EC2 Compute Node.
So, the question becomes.... Why does dnsmadeeasy have incorrect IP Address information for eight mail servers in the domain williamsmoving.com. Since dnsmadeeasy.com is the authoritative name service for williamsmoving.com, it would seem that this is likely a result of incorrect information having been provided to dnsmadeeasy.com.
The other thing somewhat quirky... even though the same IP Address is retrieved from all six name servers for all eight mail servers... the header on that section of the report still reads "All hostnames referenced by MX records resolve to different IP Addresses", which most certainly is not reflected in the displayed results. I've bounced that up to the DNSStuff.com people.