Testing lightning components feb 15th 2018
0 likes317 views
The document outlines a March webinar focused on testing in the Salesforce Lightning Experience, emphasizing the challenges associated with manual testing and the limitations of existing tools. It highlights Provar's solutions for addressing these challenges, including demos of testing Lightning components and functional tests across both Lightning and Classic environments. The presentation covers the Provar roadmap, migration strategies, and offers guidance on reusable test cases.
![Technical: Visualforce Field ids
Visualforce
Custom field id="j_id0:j_id1:j_id2:j_id32:j_id33"
Lightning has encapsulated VF in an iFrame
apex:inputField[@value = ‘{!Opportunity.Name}’]"
Managed by Provar metadata](https://image.slidesharecdn.com/testinglightningcomponentsfeb15th2018-180215170624/85/Testing-lightning-components-feb-15th-2018-17-320.jpg)
Testing lightning components feb 15th 2018
- 2. March Webinar Register now: provartesting.com/whats-new-webinar
- 3. Head of Salesforce Engineering • Provar Salesforce roadmap • Salesforce.com relationships • Lightning Workstream Lead • Salesforce SME Background • 10y Salesforce, 5x Certified, 3x DF Speaker • 5x AppExchange & 3x ISV Apps • 2x CTO of UK Platinum SIs • 2x Provar customer • 2x Lightning greenfield implementations • 1x Lightning migration (350 users, 2x adoption to 90%) Richard Clark Twitter/LinkedIn: @RichClark808 About Me
- 4. Forward Looking Statement While we’re not listed on the NYSE, I am going to talk about and demonstrate some future functionality today. I’ll try and call out when I’m using something new we’re developing right now. Please do not make purchasing decisions based solely on this presentation (...but if you do feel free to mention my name!)
- 5. Testing in Lightning - Overview ● Why Provar? ● Lightning Experience Challenges ● Demo - Testing Lightning Experience ● Demo - Testing Flexipages (Declarative) ● Demo - Testing Custom Components (Code) ● Provar Roadmap for Lightning ● Lightning Migration Strategy ● Further Reading ● Q&A
- 7. What’s the problem? Manual testing is costly and time consuming. Coded test automation is not scalable. Generic test tools can’t move fast enough.
- 8. Salesforce Testing Challenges Reliability I waste time updating field locators when testing across different environments. Complexity It’s hard to test advanced features like Visualforce, Salesforce CPQ or a Service Cloud Console. Reusability I have to recreate all my Classic tests for the new Lightning UI. “ ” “ “ ” ” Salesforce customers often come to us with these challenges:
- 9. Some of our best features No Code Lightning ready DevOps Support Salesforce specialist Aligned to the Salesforce product roadmap. Deep feature support including Console, Visualforce and CPQ Build tests in the browser with point-and-click plus Eclipse IDE Connect to Continuous Integration and Version Control, test across multiple browsers and devices. Salesforce DX compatible. Build and reuse tests across Classic, Lightning and Mobile
- 10. Lightning Experience Functional and Technical Challenges
- 11. Before we continue … Term Definition Classic The existing user interface (a.k.a. Aloha) Lightning Experience New user interface, a.k.a. Lightning, LEX Lightning Application Custom Applications consisting of Flexipages and Component Tabs rather than a Classic App in Lightning Experience Lightning Component Components written in Aura, either by Salesforce (Standard) or a Developer (Custom) Flexipage Lightning pages developed using point & click PageObject Reusable mappings created by Provar to locate items in Visualforce, Custom Components and generic websites
- 12. What’s special about Lightning? Buttons & Actions Desktop First Multi Page App Fixed page design Classic Combined Action Menu(s) * Mobile first Single Page App, Event Architecture Flexible page design Improved User Journeys Lightning/Salesforce Mobile
- 13. Functional: Related Lists Managed by Provar metadata
- 14. Functional: Layouts are Modal Managed by Provar metadata
- 15. Functional: Lookups are Picklists Managed by Provar metadata
- 16. Technical: Salesforce Field ids Salesforce Layouts Classic: Standard fields id="opp3" Custom fields id="00NB0000002ChXz" Lightning: Standard fields id="430:7466;a" Custom fields id="1138:7466;a" Managed by Provar metadata
- 17. Technical: Visualforce Field ids Visualforce Custom field id="j_id0:j_id1:j_id2:j_id32:j_id33" Lightning has encapsulated VF in an iFrame apex:inputField[@value = ‘{!Opportunity.Name}’]" Managed by Provar metadata
- 18. Change Impact for Existing Tests Layout Navigation, multiple sub-tabs and sections per page Error Messages in Field Messages and Alert messages Addition of Currency symbol(s) in Edit Addition of Percentage signs in Edit Changes in user journeys ● for related objects ● for Campaigns Requires Provar test updates
- 20. Recap What we just saw: ● Reused a Classic test for a New Lead Conversion to Lightning ○ No changes ● Tests that work in both Classic and Lightning ○ No changes ● Creating a new test for Lightning Console with Test Builder ● For standard pages you don’t need to author special Lightning tests ● Note: Always leave you test user in Classic mode, or salesforce will auto-redirect to Lightning
- 22. Recap What we just saw: ● Test for Flexipage after admin updates the page ● Provar is immune to changes to tab ordering, additions ● Limitations to moving components on a page Important Note! ● You may need to refresh your Provar metadata with changes and remap the step for complex changes.
- 24. Lightning Component Challenges Here are some of the issues with testing Lightning Components: 1. Lightning is not 1:1 vs Classic 2. Salesforce’s Aura framework is a moving target 3. The Lightning Design System is a moving target 4. Lightning HTML markup & CSS varies by component usage 5. Custom components do not enforce Unit Testing 6. Lack of maturity in how components are developed
- 25. Lightning Component Challenges How can Provar help with this? 1. Lightning is not 1:1 vs Classic 2. Salesforce’s Aura framework is a moving target 3. The Lightning Design System is a moving target 4. Lightning HTML markup & CSS varies by component usage We take care of these as fast as we can so you don’t have to 5. Custom components do not enforce Unit Testing 6. Lack of maturity in how components are developed You have to look after these through Development Standards
- 26. Demo 4 - Simple Custom Form
- 27. Recap What we just saw: ● Testing Inline Edit in Lightning ● Testing a custom Lightning component form within a Flexipage ● New AuraBy locator ● Interacting with multiple forms in parallel ● Custom components failing ‘silently’
- 28. Demo 5 - Master Detail
- 29. Recap What we just saw: ● Adding Opportunities & Line Items ● Populating & Asserting values in nested Custom Components ● Testing components in a table iteration ● Validating field changes from Lightning Events (no submit)
- 30. Demo 6 - Lightning in Visualforce
- 31. Recap What we just saw: ● Testing a Custom Lightning in a Visualforce page ● Support for Classic using Lightning Components ● Testing Lightning even if you’re not yet migrating to LEX Note ● Lightning Events are not supported by VisualForce, so expected behaviour may be different… ● Components can be used in Salesforce Mobile
- 32. Provar Salesforce Roadmap as of Feb 2018
- 33. Current Lightning Feature Support To summarise, we can already: ● view, create, edit, delete records like Classic ● navigate List Views & Related Lists like Classic ● click buttons like Classic ● test Console, Standard and Mobile (emulator) Apps ● reuse your Classic Visualforce pageobjects ● test some flexipage components ● test some Custom Lightning Components (v1.9+), including nested components, iterations and dynamic components All non-UI tests APIs fully supported
- 34. H2 2018 Additional Component Support Increased custom component support, for standard aura component library. Full standard flexipage component support H1 2018 Flexipage & Custom Component Support Increased coverage for Salesforce flexipage components & Actions without manually edited PageObjects (e.g. Path, Custom Actions). Basic support for Custom Components using best practice development that you’ve seen today. 2017 Lightning Ready Standard LEX support plus PageObjects support for custom development. Limited Flexipage support. 2019 Future Roadmap Support for special Salesforce components for complimentary applications (horizontal and vertical). Provar Lightning Roadmap ◈ ◈ ◈ ◈◈ ◈ ◈ ◈ ◈ ◈ ◈ ◈ ◈
- 35. Work In Progress Enhancements include the following: ● New Lightning URL format (one/one.app -> lightning) ● Special Standard & Custom Actions ● Tab dropdown menus ● Path (fields, text and navigation) ● Highlights Panel fields ● Utility Bar & Macros ● Lightning Bolt Communities ● Additional ui: and lightning: base component support ● On Device Mobile App Testing
- 37. Lightning Test Strategy Is the project planning major functionality changes? Are Visualforce pages being replaced with Lightning components? Are some users staying on Classic or is it ‘Big Bang’? Option A: A single test suite to run with Classic and Lightning Option B: Separate tests for Classic and Lightning Option C: Create new tests
- 38. Lightning Migration Strategy 1. Trailhead Courses 2. Lightning Readiness Report 3. Run existing tests in Lightning mode a. Include findings in your Lightning Effort Score 4. Majority of tests using standard configuration should pass a. Some functionality will be re-implemented by your SF Admins/Devs b. Some tests will need to be updated (different Lightning user journeys) c. Some tests will fail because they’re not visible in Lightning 5. Run tests for both environments daily while you convert
- 39. Further Reading Beginners: Salesforce Trailhead: Introduction to Lightning Experience Provar Tutorial: Lightning Testing Classic vs Lightning Feature Comparison Advanced: White Paper: Testing Custom Lightning Components
- 40. March Webinar Register now: provartesting.com/whats-new-webinar
- 43. Tips 1. Test user must default to Classic 2. Let Provar do page navigation 3. Create Environment variable (see Lightning QS) 4. Contains or ends with 5. Use IF … THEN … ELSE 6. Create callable tests 7. NumberFormat() in Asserts to handle £$€ and % calculations 8. Speak to your development team first!