Adapting to the New Behavior

Oct 13, 2025 by talynt.org 110 views

Introduction

Pharo 13 has introduced a change in the default precision of the closeTo: method, which has caused several tests to fail. In this article, we will explore the impact of this change and provide guidance on how to adapt to the new behavior.

Understanding the Change

The closeTo: method is used to check if a value is close to a given target value within a certain precision. In Pharo 13, the default precision of this method has been changed, which has affected several tests that relied on the previous behavior.

Affected Tests

The following tests have been identified as failing due to the change in the default precision of closeTo::

BlAnimationExamplesTest
- #test_4_2_sequential_first_step_fullDuration
- #test_4_1_sequential_first_step_halfOfDuration
- #test_4_2_sequential_first_step_fullDurationAndHalf
- #test_5_1_sequential_first_secondStep_halfDuration
BlScalableElementExamples
- #exactContentSmallerInExactScalableFitAll

Impact of the Change

The change in the default precision of closeTo: has caused the tests to fail because the values being checked are no longer considered close to the target values within the expected precision.

Adapting to the New Behavior

To adapt to the new behavior, you can take the following steps:

Update the tests: Modify the tests to use a specific precision when calling closeTo:, rather than relying on the default precision.
Use a more robust assertion: Instead of using closeTo:, consider using a more robust assertion method, such as assert:, which allows you to specify a tolerance for the comparison.
Review the code: Review the code that is using closeTo: to ensure that it is not relying on the default precision and is instead using a specific precision or a more robust assertion method.

Example Code

Here is an example of how you can update a test to use a specific precision when calling closeTo::

| animation progress |

animation := BlAnimation new.
animation progress closeTo: 0.1818181 precision: 0.00001.

In this example, the closeTo: method is called with a specific precision of 0.00001, rather than relying on the default precision.

Conclusion

The change in the default precision of closeTo: in Pharo 13 has caused several tests to fail. To adapt to the new behavior, you can update the tests to use a specific precision, use a more robust assertion method, or review the code to ensure that it is not relying on the default precision. By taking these steps, you can ensure that your tests continue to run successfully in Pharo 13.

Recommendations

Update your tests: Modify your tests to use a specific precision when calling closeTo:, rather than relying on the default precision.
Use a more robust assertion: Consider using a more robust assertion method, such as assert:, which allows you to specify a tolerance for the comparison.
Review your code: Review your code to ensure that it is not relying on the default precision and is instead using a specific precision or a more robust assertion method.

Additional Resources

Pharo 13 documentation: Consult the Pharo 13 documentation for more information on the closeTo: method and its behavior.
Pharo community: Reach out to the Pharo community for guidance and support in adapting to the new behavior.

FAQs

Q: What is the default precision of closeTo: in Pharo 13? A: The default precision of closeTo: in Pharo 13 is different from the previous version.
Q: How can I update my tests to use a specific precision? A: You can update your tests to use a specific precision by calling closeTo: with a specific precision, such as precision: 0.00001.
Q: What are some alternatives to closeTo:? A: Some alternatives to closeTo: include using a more robust assertion method, such as assert:, or using a specific precision when calling closeTo:.
Frequently Asked Questions (FAQs) About the Change in closeTo: Default Precision in Pharo 13 =============================================================================================

Q: What is the default precision of `closeTo:` in Pharo 13?

A: The default precision of closeTo: in Pharo 13 has been changed from the previous version. This change has caused several tests to fail.

Q: Why did the default precision of `closeTo:` change in Pharo 13?

A: The change in the default precision of closeTo: was made to improve the accuracy and robustness of the method. However, this change has affected several tests that relied on the previous behavior.

Q: How can I update my tests to use a specific precision?

A: You can update your tests to use a specific precision by calling closeTo: with a specific precision, such as precision: 0.00001. This will ensure that your tests continue to run successfully in Pharo 13.

Q: What are some alternatives to `closeTo:`?

A: Some alternatives to closeTo: include using a more robust assertion method, such as assert:, or using a specific precision when calling closeTo:. You can also consider using a different method, such as approximate:, which allows you to specify a tolerance for the comparison.

Q: How can I review my code to ensure that it is not relying on the default precision?

A: To review your code, you can search for instances of closeTo: and check if a specific precision is being used. If not, you can update the code to use a specific precision or a more robust assertion method.

Q: What are some best practices for using `closeTo:` in Pharo 13?

A: Some best practices for using closeTo: in Pharo 13 include:

Using a specific precision when calling closeTo:
Using a more robust assertion method, such as assert:
Reviewing your code to ensure that it is not relying on the default precision
Considering alternative methods, such as approximate:

Q: How can I get help if I am experiencing issues with `closeTo:` in Pharo 13?

A: If you are experiencing issues with closeTo: in Pharo 13, you can reach out to the Pharo community for guidance and support. You can also consult the Pharo 13 documentation for more information on the closeTo: method and its behavior.

Q: What is the impact of the change in `closeTo:` default precision on my code?

A: The change in the default precision of closeTo: may affect your code if it relies on the previous behavior. You may need to update your code to use a specific precision or a more robust assertion method to ensure that it continues to run successfully in Pharo 13.

Q: Can I revert to the previous behavior of `closeTo:` in Pharo 13?

A: It is not recommended to revert to the previous behavior of closeTo: in Pharo 13. Instead, you should update your code to use a specific precision or a more robust assertion method to ensure that it continues to run successfully in Pharo 13.

Q: What are some resources for learning more about the change in `closeTo:` default precision in Pharo 13?

A: Some resources for learning more about the change in closeTo: default precision in Pharo 13 include:

The Pharo 13 documentation
The Pharo community
Online forums and discussion groups
Pharo 13 tutorials and guides

Conclusion

The change in the default precision of closeTo: in Pharo 13 has caused several tests to fail. To adapt to the new behavior, you can update your tests to use a specific precision, use a more robust assertion method, or review your code to ensure that it is not relying on the default precision. By taking these steps, you can ensure that your tests continue to run successfully in Pharo 13.