Which statements are true regarding how to run inspections? Name two.

For running inspections in Guidewire, the process involves specific methods that enhance code quality and help developers catch potential issues.

Triggering manually in Studio using the 'Analyze -> Inspect Code' function is a straightforward and commonly used approach. This method allows developers to initiate inspections on demand, providing immediate feedback on code quality and style compliance. It is essential for ensuring that the code meets the project's standards and does not contain errors before it is committed.

Running inspections as background tasks in the Gosu Editor offers another layer of convenience. While a developer is coding, the system can automatically check the code in the background, providing insights and alerts without interrupting the development workflow. This feature helps maintain a high standard of code quality continuously without requiring additional steps by the developer.

Thus, combining the ability to trigger inspections both manually and as background tasks reflects the flexibility and support for maintaining code integrity within the development environment. These aspects emphasize the importance of continual inspection in a coding process, making the two mentioned options valid for understanding how inspections function in Guidewire.