Why use "which" to check existed file?

[wzhen12]

./runtests -f sdsi/tests
==> /tmp/stderr <==
|0816_074419.075|ERROR| common.sh:155:block_test() - block_test() is called by common.sh:571:check_fms_list()|
|0816_074419.077|ERROR| common.sh:156:block_test() - Result ====BLOCK==== : No family model stepping list file:sdsi_fms_list found|

The function of check_fms_list is in common.sh for checking existed files.
$fms_list_file is the existed file.
"
list_file=$(which "$fms_list_file" 2>/dev/null)
[[ -n "$list_file" ]] || block_test "No family model stepping list file:$fms_list_file found"
"
Why use "which" to check the existed file of "$fms_list_file"?
It should get the not right results.

[qwang59]

The sdsi_fms_list file should have its execute permissions, which has been addressed in the recent patch.

[wzhen12]

You mean that we can copy sdsi_fms_list to such as /usr/bin or set the local path to $PATH?
If not, the command of "which" will not find sdsi_fms_list in local path.
The command of "which" only find the related command with execute attribute in /usr/bin or $PATH.

Or we will not use the command of "which" to check the local file?