Emergency Bug Fix (EBF) Build Automation

Aabid Hussain
Project Guide: Sabeeha Sultana
Dept. Of MCA

PESSE
Agenda

• Introduction

• Problems

• Salient Features

• Test Cases

• Queries

2
Introduction

• MercuryEBFBuilder is an automation tool used to

easily build Mercury EBFs with accuracy, less time,
consistency and reduced learning curve.

3
USE CASE DIAGRAM
Mercury Emergency Bug Fix (EBF) Builder

<<include>> <<extend>>
UNIX
Login to respective
machine
Pre-Build <<extend>>

Win
<<include>>
Change permission and
Sync check-in files

Run-Build Build EBF

<<include>>

Build & Release

Create EBF
Installer
Engineer <<include>>
FTP shipping
<<include>>
file(s)

Post-Build
Publish mail
<<include>>

4
Problems
• Manual creation of EBF Installer

• EBF building process was done on remote machine and client

needs to remain connected to remote machine till process
completes.
• Much of developers effort and time was used for setting up the
environment and managing the process.
• There was no chance of going to previous step if the process
fails in some particular stage.
• At a particular time, developer was able to work on EBF
building only.

5
Salient Features
• Complete automation of creating EBF Installer.

• Support for system specific EBF basedir

• Option to run packebf utility.

• Now the EBF building can be started from any stage.

• EBFs can be developed on local machine and then sent to remote

machine
• Once Process is started, developer can work on other things also.

• EBF Build will not fail if there are no checkin files to copy but a
proper message will be displayed.
• Files can be renamed also

6
 sample-properties.xml
<mercury-ebf-properties>
<ebf-id>10609</ebf-id>
<!-- e.g. 1234, 5400 -->

<ebf-cr-no>274566</ebf-cr-no>
<!-- e.g. 123456, 239165 -->

<platform>lin-x64</platform>
<!-- aix-ppc32, aix-ppc64, hp-x32, hp-x64, hp-ia64, lin-x32, lin-x64, lin-ia64, lin-z64 -->
<!-- sol-sp32, sol-sp64, sol-x64, win-x32, win-x64, win-ia64 -->

<pc-version>861hf14</pc-version>
<!-- 861hf1, 861hf2, 861hf3, 861hf4, 861hf5, 861hf6, 861hf7, 861hf8, 861hf9, 861hf10, 861hf11, 861hf12 etc.-->

<shipping-files
dir="powrmart/pmbuild/bin/${release.dir.name}">
<install-location> </install-location>
<file>
<actual-file-name></actual-file-name>
<renamed-name></renamed-name>
<install-location> </install-location>
</file>
<file>
<actual-file-name></actual-file-name>
<renamed-name></renamed-name>
</file>
</shipping-files>

7
 sample-properties.xml (cont.)
<!-- details for packebf utility to publish Ebf -->
<release-date>Dec 2, 2011</release-date>
<!-- Aug 8, 2010 -->
<symptoms>
<![CDATA[
INFA274566 - SQL transformation on Sybase which fails with PMSQL_50065 due to a trigger on underlying
table ignores rest of the DML statements in the SQL transformation.
]]>
</symptoms> <description>

<![CDATA[
]]>
</description>

<fixtype>Service8</fixtype>

<!-- jar jsp jarjsp Client Service8 PCSF -->

<solution>

<![CDATA[

Apply this EBF fix.

]]>

</solution>

<notes> 8
Run options

9
Notes

• 1. buildEbf option does not execute “runPackEbf”

target. Instead, we need to execute “runPackEbf”
explicitly with option 5.

10
Test Cases
Serial No. of test case
1
Name of test Starting/Running Automation

Feature being tested Start Automation

Sample Input Automation suite

1. The Automation should run smoothly till
completion.
Expected output
2. The result of the automation should write to log
and output file
1.Automation process is running properly.
3. The result of the automation has been written log
Actual output
and output files

Remarks Pass

11
Serial No. of test case
2

Name of test Running Individual phases of automation

Feature being tested Automation phases as separate units

Sample Input Automation suite

1. The Automation phase should run
Expected output
smoothly till completion.

1.Each Automation phase is running properly.

Actual output

Remarks Pass

12
Serial No. of test case
3

Name of test Validating properties.xml file data

Feature being tested Validating the Input data

Sample Input Automation suite

1. The Automation process should run smoothly till

Expected output completion when correct input is given.
2. Error should be generated when wrong input is given

1.The automation process works properly when correct input

Actual output was given and for wrong input the process could not triggered
off and proper message was displayed

Remarks Pass

13
Serial No. of test case
4

Name of test Check for remote transfer of EBF

Feature being tested EBF transfer from local machine to server

Sample Input Automation suite

1. Once the EBF has been built on local
Expected output
machine it should be sent to server.

1.EBF was properly sent to desired location.

Actual output

Remarks Pass

14
 Q&A

Thank You

15