Add SpeedWeightingTest with 7 new unit tests #1
+122
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ajout de tests unitaires pour SpeedWeighting
Changements
Création d'une nouvelle classe
SpeedWeightingTest
avec 7 cas de test documentés :testCalcEdgeWeightNormal
— calculedistance/speed
quand la vitesse est > 0.testCalcEdgeWeightZeroSpeed
— retourneDouble.POSITIVE_INFINITY
quand la vitesse = 0.testCalcEdgeWeightReverse
— utilise la vitesse en sens inverse.testCalcEdgeMillis
— calcule le temps en millisecondes = poids * 1000.testCalcMinWeightPerDistance
— vérifie que le poids minimal est l’inverse de la vitesse max.testGetName
— confirme quegetName()
retourne"speed"
.testHasTurnCosts
— valide quehasTurnCosts()
est vrai avec un TurnCostProvider.Mise à jour de
core/pom.xml
pour ajouter Mockito v5.19.0 (scope test).Résultats
SpeedWeighting
est améliorée.