Most of the changes done in this issue are to improve the developer experience, they have no real impact to users. The only part that requires manual testing is the new features available to plugins. This issue only needs to be tested in 1 device. This test requires looking at the Javascript console, so I guess it's better that it's tested by a developer. Install the plugin attached to this issue in the local folder of your site. In the app, login in the site and open the "More" tab. Check that you see an option named "Test signals". Open the Test signals option. Check that you see a form with a name (empty), a year (set to 2024) and a message saying "Hello , you will turn 0 in 2024.". Open the Javascript console and empty it so you can better see the messages. Filter them to only see errors, that way you will have less distractions. Enter something in the name. Check that, after each change, the message displayed to the user is updated to reflect the new name.  Check that, after each change, a log appears in the console saying that the name was modified. Please notice there is also a message in the console saying that the effect was destroyed. I'm not sure if this is a bug or a feature by Angular, but it seems that, if an effect uses a model, the effect is recreated every time the model changes. Modify the year. Check that, after each change, the message displayed to the user is updated to amount of years you will turn in 2024. Check that no message appears in the console in this case (we use Angular's untracked for the year). Clean the console and perform a Pull To Refresh. Check that you see a message in the console saying that the effect was destroyed (the component is recreated, so we need to destroy the previous effect). Leave the page using the back button.  Check that you see a message in the console saying that the effect was destroyed.