- Force.com Enterprise Architecture - Second Edition
- Table of Contents
- Force.com Enterprise Architecture - Second Edition
- Credits
- Foreword
- About the Author
- Acknowledgements
- About the Reviewers
- www.PacktPub.com
- Customer Feedback
- Preface
- 1. Building, Publishing, and Supporting Your Application
- Required organizations
- Introducing the book's sample application
- Package types and benefits
- Creating your first managed package
- Package dependencies and uploading
- Becoming a Salesforce partner and benefits
- Introduction to AppExchange and listings
- Installing and testing your package
- Licensing
- Providing support
- Customer metrics
- Trialforce and Test Drive
- Summary
- 2. Leveraging Platform Features
- Packaging and upgradable components
- Understanding the custom field features
- Understanding the available security features
- Platform APIs
- Localization and translation
- Building customizable user interfaces
- E-mail customization with e-mail templates
- Process Builder, Workflow and Flow
- Social features and mobile
- Summary
- 3. Application Storage
- Mapping out end user storage requirements
- Understanding the different storage types
- Reusing the existing Standard Objects
- Importing and exporting data
- Options for replicating and archiving data
- External data sources
- Summary
- 4. Apex Execution and Separation of Concerns
- 5. Application Service Layer
- 6. Application Domain Layer
- Introducing the Domain layer pattern
- Implementation design guidelines
- Domain class template
- Implementing Domain Trigger logic
- Implementing custom Domain logic
- Object-oriented programming
- Creating a compliance application framework
- An Apex interface example
- Testing the Domain layer
- Calling the Domain layer
- Updating the FormulaForce package
- Summary
- 7. Application Selector Layer
- 8. User Interface
- Which devices should you target?
- Introducing Salesforce Standard UIs and Lightning
- Leveraging the Salesforce standard UIs
- Generating downloadable content
- Generating printable content
- Client server communication
- Managing limits
- Object and field-level security
- Managing performance and response times
- Using the Service layer and database access
- Considerations for using JavaScript libraries
- Custom Publisher Actions
- Creating websites and communities
- Mobile application strategy
- Custom reporting and the Analytics API
- Updating the FormulaForce package
- Summary
- 9. Lightning
- Building a basic Lightning user interface
- Lightning architecture
- FormulaForce Lightning Components
- Making components customizable
- Integrating with Lightning Experience
- Lightning Out and Visualforce
- Integrating with communities
- Testing
- Updating the FormulaForce package
- Summary
- 10. Providing Integration and Extensibility
- Reviewing your integration and extensibility needs
- Force.com platform APIs for integration
- Application integration APIs
- Exposing Lightning Components
- Extending Process Builder and Visualflow
- Alignment with Force.com extensibility features
- Extending the application logic with Apex interfaces
- Summary
- 11. Asynchronous Processing and Big Data Volumes
- 12. Unit Testing
- 13. Source Control and Continuous Integration
- Development workflow and infrastructure
- Developing with Source Control
- Hooking up Continuous Integration
- Releasing from Source Control
- Automated regression testing
- Summary
- Index
While Apex tests are very much a key tool in monitoring regressions in your application, the limitations and scope of functionality they can test is small, particularly to perform volume or user interface testing (clients using JavaScript for example).
Note
You might wonder why the Ant script used by Jenkins deploys twice, as the check deploy to the packaging org will confirm whether the Apex code compiles and that all Apex tests complete successfully. The reason is that having the build org deployed with the latest build allows for it to go on to be used for other purposes, such as executing further regression testing steps.
Here are some considerations to implement further testing approaches:
- It is possible to execute the Apex code from the Ant scripts using the approach described earlier in this chapter, when we populated the developer org with sample data by calling the
SeasonService.createTestSeasonmethod. You can extend this approach by using loop constructs within Ant to create volume data or start more Batch Apex jobs (Apex tests only permit a single chunk of 200 records to be processed), pause for completion, and assert the results. - The Salesforce data loader tool is actually a Java program with a command-line interface. Thus, you could consider using it to load data into a build org to test against different datasets, used in combination with the preceding Apex code executed to clean records between tests.
- Once you have the data loaded into the build org, you can execute tests using a number of Salesforce testing tools. For example, the Selenium WebDriver tool is an excellent choice, as it provides a headless mode (no need for a physical screen) and can be run on multiple operating systems. This tool allows you to test Visualforce pages with large amounts of JavaScript (http://docs.seleniumhq.org/projects/webdriver/).
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.