Skip to content

Preconfigure the test app to use Solid Queue/Mission Control - Jobs#3618

Draft
taylor-steve wants to merge 3 commits intomainfrom
solid-queue
Draft

Preconfigure the test app to use Solid Queue/Mission Control - Jobs#3618
taylor-steve wants to merge 3 commits intomainfrom
solid-queue

Conversation

@taylor-steve
Copy link
Contributor

Description

This pre-configures Solid Queue/Mission Control - Jobs for the test app. This could be a potential quality of life improvement for developers. It's been brought up in the past that the behavior of jobs (e.g., indexing & indexing progress) can be confusing when using the test app for development without an Active Job backend installed & configured.

This is only for the test app in the development environment. It does not impact template installs.

Copy link
Member

@jcoyne jcoyne left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would encourage the community to skip this one. Although it does successfully show that Spotlight can work with solid queue, it adds more dependencies into testing and generally makes it more complicated. I think we can all agree that the engine is hard to maintain, so we should strive for simplicity.

@taylor-steve
Copy link
Contributor Author

@jcoyne thanks for the input. This is only for the test app, and only when not running in CI. Do you have an alternative approach to suggest to remove the burden of installing an active job backend for local developers? Are you opposed to the ask in general (to reduce this friction for new/less active devs), or only that it's touching test related code? I'm all for simplicity.

@jcoyne
Copy link
Member

jcoyne commented Jan 8, 2026

@taylor-steve the test app is still used for doing tests locally. In this case we are adding complexity as we are running different code in the developers local tests than we are running in CI. That's the kind of thing that gets hard to understand when a problem arises. Isn't the asynchronous ActiveJob adapter already installed by default in rails?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants