testRigor & Salesforce
  • NO-CODE UI TESTING: Guide for testRigor & Salesforce
  • Getting Started
    • Get a Salesforce Hands-On Playground Org (free)
    • Get testRigor (free) and create a Test Suite
    • Create Test Case (T00001)
    • Navigation in Salesforce
    • Navigation in testRigor
  • BASIC TEST CASES
    • Record, edit and play a Test Case (T00002)
    • Create and convert a Lead (T00003)
    • Create more records (T00004)
    • Check Account Validation Rule (T00005)
  • ADVANCED TEST CASES
    • Account Action and List View Button (T00006)
    • Validate Field Value Using REST API (T00007)
    • E2E: Lead entry (Titan) ➔ Salesforce ➔ Email
  • OTHER TEST SCENARIOS
    • Submit a Test Lead
    • TH: Opportunity Won THEN Create Contract
    • Monitor data in your website
    • Monitoring in Production
  • FLOW TEST CASES
    • Screen Flow: Update Email Address
  • E-BIKES SAMPLE APP
    • E-Bikes sample app description
    • testRigor version of the UTAM TEST (EBIKES-00001)
    • Product Explorer - Electra X3 (EBIKES-00002)
    • Reseller Order - Create (EBIKES-00003)
    • Case - Create (EBIKES-00004)
  • LWC RECIPES SAMPLE APP
    • LWC Recipes sample app description
    • Test Case for LWC Recipes (LWC-00001)
  • CORAL CLOUDS SAMPLE APP
    • Coral Clouds sample app description
    • Experience - Generate Description using AI (CC-00001)
    • Experience - Generate Reviews Summary using AI (CC-00002)
  • MORE INFORMATION
    • About testing
    • About testing in Salesforce 🤔
    • About test automation
    • About Test-Driven Development (TDD)
    • About testRigor
    • About using testRigor
    • About other solutions
  • FEEDBACK
    • Questions? - Comments!
Powered by GitBook
On this page
  • Scenario
  • Immediate action
  • Defensive Test Case against observed defects
  1. OTHER TEST SCENARIOS

Monitor data in your website

PreviousTH: Opportunity Won THEN Create ContractNextMonitoring in Production

Last updated 3 months ago

Scenario

On 2024-12-16, a random Salesforce Dude observed defects in the Salesforce public website:

  • 26 MVPs had bad links in their card

    • defect fingerprint: "https:"

  • one MVP had Salesforce record id in place of her last name

    • defect fingerprint: "005"

  • several MVPs have garbled details

    • defect fingerprint "%"

  • sometimes images are not shown

Immediate action

Salesforce was informed about these defects with the following steps to reproduce:

1. Navigate to: https://trailhead.salesforce.com/mvp/#meet
2. Click button: "Meet Them"
3. Observe: First cards show up.
4. Hit Ctrl-F and type "Show More"
5. Observe: Focus goes to (and stays on) button "Show More"
6. Repeatedly click "Show More" until all MVS show up
7. Hit Ctrl-F and type "http"
8. Observe: 26 results
9. Scroll to first result
10. Observe the bad link
f.ex: Jen Nelson has this link: 
- linkedin.com/in/https://www.linkedin.com/in/jen-nelson-77198218

Defensive Test Case against observed defects

In order to ensure of the integrity of data in the Salesforce.com MVP Hall of Fame, this test case could be scheduled to run daily: 

open url "https://trailhead.salesforce.com/mvp/#meet"
click "Show More" 25 times

check that page doesn't contain "https:"
check that page doesn't contain "005"
NO-CODE UI TESTING: Guide for testRigor & Salesforce
10MB
Salesforce MVP Hall of Fame 2024-12-16.pdf
pdf
2024-12-21
2025-01-01