Re: [chirp_devel] trouble with tests and custom steps logic

It seems as if chirp is still trying to set 5.0khz step in Edges test, although it's not valid_tuning_step defined in the radio model.

Well, in this case, it's just the test doing it, right?

If the test is trying to set a memory with a tuning step that is not in the list of valid ones, then the test is not testing a reasonable scenario. I think you can just tweak the test to honor the valid_steps in this case.