adding builtin usage tests

[Idanh-starkware]

Type

• feature
• bugfix
• dev (no functional changes, no API changes)
• fmt (formatting, renaming)
• build
• docs
• testing

Description

Breaking changes?

• yes
• no

---

This change is 

[Idanh-starkware]

• adding builtin usage tests #205 👈 (View in Graphite)
• fixing execute_task_hints.rs tests #204 : 2 other dependent PRs (#206 , #208 )
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[OmriEshhar1]

@OmriEshhar1 reviewed 2 of 2 files at r1, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @YairVaknin-starkware)

---

crates/cairo-program-runner-lib/src/hints/builtin_usage_hints.rs line 284 at r1 (raw file):

    #[rstest(finalize, case(true), case(false))]
    fn test_builtin_usage_add_other_segment(finalize: bool) {
        // Test the builtin_usage_add_other_segment function with finalize set to true.

it is tested for both finalize=true and finalize=false, isn't it?

Code quote:

with finalize set to true

[Idanh-starkware]

crates/cairo-program-runner-lib/src/hints/builtin_usage_hints.rs line 284 at r1 (raw file):

Previously, OmriEshhar1 wrote…

it is tested for both finalize=true and finalize=false, isn't it?

Yes, bad documentation.

[OmriEshhar1]

@OmriEshhar1 reviewed 1 of 1 files at r2, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @YairVaknin-starkware)