Bug 52 - Reader 2.4.7 should be treated as up-to-date Reader.
Summary: Reader 2.4.7 should be treated as up-to-date Reader.
Status: VERIFIED FIXED
Alias: None
Product: TestProduct
Classification: Unclassified
Component: TestComponent (show other bugs)
Version: unspecified
Hardware: All All
: Highest critical
Assignee: No one
URL:
Depends on:
Blocks:
 
Reported: 2018-08-07 18:16 EDT by Kuanshen An
Modified: 2018-08-16 22:50 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kuanshen An 2018-08-07 18:16:13 EDT 
Testing in build 743( with latest firmware 2.4.8),it treat Reader 2.4.7 as 'Incompatible sensor'

expect it should treat Reader 2.4.7 as 'up-to-date', what I heard that RSU should treat both 2.4.7 and 2.4.8 as up-to-date..
Comment 1 Kuanshen An 2018-08-07 18:39:05 EDT 
this scenario is part of SIT execution.
Comment 2 Brian Roberge 2018-08-07 20:06:45 EDT 
I believe 2.4.7 will never be found outside a test environment.  So we should consider it an invalid version if we find it.
Comment 3 Kuanshen An 2018-08-07 21:58:24 EDT 
Olson, Jennifer reply a mail and said how to treat 2.4.7 Reader.
"
It will be installed on FSL Algo readers as manufactured starting in Jan 2019. It will definitely be in the field, and yes should be treated as up to date "
Comment 4 Kuanshen An 2018-08-07 23:21:34 EDT 
Sujit confirmed that 2.4.7 would not be used anymore. t

This is a invalid test cases now since 2.4.8 is the only firmware available for those country deployed with RSU utility.

Resolve invalid.