Test case 1 :
1. Install 7u1b01 in normal mode -> { Expected - evar3 = XX ; Actual - evar3 = XX }
2. Update 7u1b01 to its NEXTBLD -> { Expected - evar3 = 1.7.0_01; Actual - evar3 = XX }

Test case 2 :
1. Install 7u1b01 in normal mode -> { Expected - evar3 = XX ; Actual - evar3 = XX }
2. Update 7u1b01 to its NEXTVER -> { Expected - evar3 = 1.7.0_01; Actual - evar3 = 1.7.0_01 }

Test case 3 :
1. Install 6u27b01 in normal mode -> { Expected - evar3 = XX ; Actual - evar3 = XX }
2. Install 7u1b01 in normal mode -> { Expected - evar3 = 1.6.27_01; Actual - evar3 = 1.6.27_01 }
3. Update 7u1b01 to its NEXTBLD -> { Expected - evar3 = 1.7.0_01; Actual - evar3 = 1.6.27_01 }

Test case 4 :
1. Install 6u27b01 in normal mode -> { Expected - evar3 = XX ; Actual - evar3 = XX }
2. Install 7u1b01 in normal mode -> { Expected - evar3 = 1.6.27_01; Actual - evar3 = 1.6.27_01 }
3. Update 7u1b01 to its NEXTVER -> { Expected - evar3 = 1.7.0_01; Actual - evar3 = 1.7.0_01 }


So, for the NXTVER updates the evar value is correctly updated. But for build to build updates the install is not able to recognize the old installed version and this shows evar = XX in test case 1.