user acceptance testing

1

USER ACCEPTANCE TESTING

16-09-2013

2

WHAT IS UAT

User Acceptance Test aims to ensure that the new development meets the business requirements with acceptable for the end users quality.

3

Non-regression testThe non-regression test aims to verify that after the implementation of the new development, the existing software functionalities have not been compromised.

Regression testRegression test is any type of software testing that seeks to uncover new software bugs in existing functional and non-functional areas of a system after changes, such as enhancements, patches or configuration changes, have been made to them.

New development validationThis type of UAT aims to validate that the new development meets the business requirements and works as expected

TYPES OF UAT

4

PROJECT MANAGER

UAT COORDINATOR

UAT TEAM MEMBER

IT PROJECT MANAGER

UAT ORGANIZATION – ROLES AND RESPONSIBILITIES

ACTIVITIESPROCESSES

45%

Project kick-off

5%

Preliminary Analysis

UATPreparation

UATExecution

ELABORATIONPHASE

CONSTRUCTIONPHASE

TRANSITIONPHASE

POST PROJECT

PREPARATIONPHASE

Mandate is Decided. Preparation is authorized

Scoping Contract is validated. Project authorized

Go Live Result assessment is validated. Closure authorized

IC2 IC3IC1Start of Construction

PhaseStart of Users

Acceptance Tests

Validation of the FSD

Start of QA(Internal IT) tests

Validation of the general BRD (v.1)

End of UAT

Preparation kick-off

6 7 9 10 15 1713 1816 19 2011 128

Starting date of UAT preliminary -analysis

UAT kick-off

UAT Quotation delivery date

1. Analyze general BRD2. Estimate the UAT duration/cost3. Create UAT preparation plan4. Outline UAT execution plan5. Write UAT quotation document6. Outline UAT strategy

UATPlanning

1.Planning the UAT pre-analysis2.Calculating the UAT cost3.Planning the UAT preparation4.Planning the UAT execution

UAT Preparation Start Date

UATquotation

10%

UATStrategy

UAT Preparation End Date

UATpreparation

plan

40%

defectsreport

UATsign-off

defectsregister

progressreport

testbook

updated

UATkick-off

1. Analyze detailed BRD/FSD2. Create test book3. Give feedback for the test book4. Create UAT execution plan5. Present plan to the stakeholders6. Create UAT strategy7. Validate UAT strategy8. Send UAT strategy

1. Announce UAT kick-off2. Authorize UAT work packages3. Execute work package4. Deliver work packages5. Log test results6. Report progress7. Defects/Issues management8. Announce sign-off

UAT Execution Duration Estimate

UAT Execution Start Date Update

UAT Execution End Date Update

5

A B C D

UAT ON 1 PAGE

testbook

UATexecution

plan

Close the defect

DEFECTS MANAGEMENT PROCESS

IT project manager• Receive defect• Accept/Reject defect• Deliver defect for retest

UAT coordinator• Validate defect• Send defect to IT• Issue management• Close defect• Update defect register

UAT team member• Execute test cases• Report defect to UAT coordinator• Retest defect

TemplatesInputs• Test book/log• Defect register

template

• Defect report template

Defectregister

Outputs• Defect report• Defect register

Defectreport

Time Frame

Milestones

UAT EXECUTION

Activities:1. Write a defect report 2. Validate defect3. Register defect4. Send defect to IT PM5. Accept/Reject defect6. Fix defect7. Deliver the fixed defect8. Retest defect9. Close defect10. Update defect register

Defect Is detected

Defect is closed

Validate the defectRegister defect

Send defect

Retest the defect

Fix defect

Defect is rejected/ accepted

Defect is fixed

Write defect report

Defect is sent

Defect is retested

Execute test cases

Deliver the fixed defect

Defect is delivered

Defect is validated

Accept defectReject defect Issue management

Update defect register

6

Write UAT issue report

UAT ISSUES MANAGEMENT PROCESS

Milestones

UAT team member• Write UAT issue report • Send UAT issue report to UAT coordinator• Validate the UAT issue solving

UAT coordinator• Receive UAT issue report• Validate UAT issue• Register issue in UAT issue register• Send issue to project manager• Inform for UAT issue solving• Close the UAT issue• Update UAT issue register

TemplatesInputs• Test book/log• UAT issue register

UAT issue

register

UAT EXECUTION

Activities:1. Write UAT issue report2. Validate the UAT issue3. Register UAT issue4. Send UAT issue to PM5. Accept/Reject UAT issue6. Solve the UAT issue7. Deliver UAT issue for validation8. Validate the UAT issue solving9. Close the UAT issue10. Update UAT issue register

Outputs• UAT issue report• UAT issue register updated

UAT Issue Is detected/ Defect is

rejected

UAT issue is closed

Validate the UAT issueRegister UAT issue

Send UAT issue

Validate the UAT issue solving

Solve the UAT issue

UAT issue is rejected/accepted

UAT issue is solved

UAT issue report is sent

UAT issue

report

Project manager• Receive UAT issue from UAT coordinator• Accept/Reject the UAT issue• Solve the UAT issue• Deliver the UAT issue for validation

UAT issue is validated

Close the UAT issue

Execute test cases

Deliver the UAT issue

UAT issue is delivered

UAT issue is validated

Accept UAT issueReject UAT issue

Update UAT issue register

Time Frame

7

8

HOW TO CREATE TEST BOOK STEP BY STEP

STEP 1: ANALYZE BUSINESS REQUIREMENTS (1/2)

• Identify concerned processes

• Identify concerned JetIX positions

• Identify concerned system modules

• Identify changes

• Identify concerned products

Direct Telesales Consultant shall be able to create and submit application using Jetix Application Form. The purpose is to fill in data and submit eligible application to enable granting decision. Application shall not be eligible for submitting if the mandatory fields (1, 2, 3) are not filled in.

ACTIONS:

9

10

Business requirement ID:• It is used for test scenarios and cases naming (Requirement ID BR.1.2 and scenario ID S1, S2…)

Concerned processes:• Create application• Submit application

Concerned JetIX positions:• Direct Telesales Consultant

Changes:• New controls

Concerned products:• Credit Classic• Credit Plan• Employer Loan Secured/Non Secured

Concerned system modules:• Application Form module (Backend)

STEP 1: ANALYZE BUSINESS REQUIREMENTS (2/2)

Business Requirement:

BR.1.2. - Direct Telesales Consultant shall be able to create and submit application using Jetix Application Form. The purpose is to fill in data and submit eligible application to enable granting decision. Application shall not be eligible for submitting if the mandatory fields (1, 2, 3) are not filled in.

Identify all situations, coming from the real business processes, concerned in the business requirements and group them by a common criteria:• Concerned process• Concerned changes

STEP 2: DESCRIBE THE TEST SCENARIOS (1/2)

ACTIONS:

11

12

Business requirement ID:• It is used for test scenarios and cases naming (Requirement ID BR.1.2 and scenario ID S1, S2…)

Concerned processes:• Create application• Submit application

Concerned JetIX positions:• Direct Telesales Consultant

Concerned system modules:• Application Form module (Backend)

Changes:• New controls

Concerned products:• Credit Classic• Credit Plan• Employer Loan Secured/Non Secured

Scenarios by concerned process:• Test the possibility to create application in Application Form module• Test the possibility to submit application in Application Form module

Scenarios by concerned changes:• Test the possibility to submit eligible application in Application Form module• Test the possibility to submit non-eligible application in Application Form module

Business requirement:

BR.1.2. - Direct Telesales Consultant shall be able to create and submit application using Jetix Application Form. The purpose is to fill in data and submit eligible application to enable granting decision. Application shall not be eligible for submitting if the mandatory fields (1, 2, 3) are not filled in.

STEP 2: DESCRIBE THE TEST SCENARIOS (2/2)

Identify all specific and unique situations, based on the scenarios and all other criteria:•Create all possible variations and combinations between the concerned processes, products, changes, JetIX positions, based on the criteria from the scenario

STEP 3: DESCRIBE THE PURPOSE OF THE TEST CASE (1/2)

ACTIONS:

13

14

STEP 3: DESCRIBE THE PURPOSE OF THE TEST CASE (2/2)

• Test the possibility to create application in Application Form module

• Test the possibility to submit application in Application Form module

• Test the possibility of Direct Telesales Consultant to create a JetCredit Plus application• Test the possibility of Direct Telesales Consultant to create a Credit Plan application• Test the possibility of Direct Telesales Consultant to create a Employer Loan Secured application• Test the possibility of Direct Telesales Consultant to create a Employer Loan Non-Secured application

•Test the possibility of Direct Telesales Consultant to submit a JetCredit Plus application, with filled fields 1,2,3• Test the possibility of Direct Telesales Consultant to submit a Credit Plan application, with filled fields 1,2,3• Test the possibility of Direct Telesales Consultant to submit a EMPL application, with filled fields 1,2,3• Test the possibility of Direct Telesales Consultant to submit a EMLN application, with filled fields 1,2,3

15

STEP 4: DEFINE THE PREREQUISITES

What are prerequisites:The prerequisites are the conditions which are necessary to be done before test case execution in order to be sure that there is no reason expected result to be not met. There are the inputs for the test case execution.

Tips for prerequisites definition:After defining the test case purpose, the prerequisites should be defined. The following questions that may be useful are:• Is a user account needed? If, yes – for what position?• Is customer’s EGN needed? If yes – for what type of client: new/repeat, with/without history, with/without delay, with active/inactive credits, etc.?• Is a specific credit needed? If yes – from which product? In what status? DPD = ? without/with financed or monthly insurance, with/without payments?, etc.• Is some event needed to happen?• Is time simulation needed?

Test Case Purpose Prerequisites

Test the possibility of JCP Sales Representative to add client’s Car data in After Sales front end module in JetIX when the client is not in delay

Test account for JCP Sales Representative, client’s EGN not in delay

Test the possibility of JCP Branch Manager to add Landline Phone After Sales front end module in JetIX when the client is in delay, DPD>0

Test account for JCP Branch Manager, client’s EGN in delay, DPD>0

Example:

16

Definition:Test steps are a detailed sequence what have to be done in order to achieve the expected result of a certain test case. Steps need to be precise, non ambiguous and easy to follow.

Example:

Tips for test steps definition:When writing test steps it is necessary to specify the sequence of each action. The points that should be specified are:• The system where the user should log in• The position which the user should be logged-in with• The access path which the user should follow• The functionalities (buttons, links, etc.) names which the user should select

Test Case Purpose Test Steps


1.Log in Jetix as JCP Sales Representative2.Select menu “Обслужване” – “Данни за клиент”3.Enter client’s EGN – button “Search”4.Select tab “Данни за клиента”5.Add values in Car data block

STEP 5: DEFINE TEST STEPS

[email protected] 17

Definition:Test data is the data which has been specifically identified and will be used in test case execution. Note that test data set is not necessary for all test cases.

Tips for test data set definition:Once the test cases are written, test data characteristics for each test case should be defined according to the UAT principles:• Assign one and the same test data for more than one test case when it is possible• Prioritize the execution order of those test cases where one and the same test data is assigned• Make a file where the test data can be easily tracked• Prepare test data set before launching the UAT• Before start executing the test steps, check if test data distributed to the test case are actually eligible for it

Example:

Test Case Purpose Prerequisites Test data ID

Execution order EGN


Test account for JCP Sales Representative, client’s EGN not in delay

EGN-1 1 6606060606

Test the possibility of JCP Branch Manager to add Landline Phone After Sales front end module in JetIX when the client is in delay, DPD>0

Test account for JCP Branch Manager, client’s EGN in delay, DPD>0

EGN-1 2 6606060606

STEP 6: DEFINE TEST DATA SET

TRACEABILITY RULES

18

Formula:

REQUIREMENT ID + LETTER “S” + NUMBER OF THE SCENARIO = SCENARIO ID where “S” means Scenario

SCENARIO ID + LETTERS “TC” + NUMBER OF TEST CASES = TEST CASE IDwhere “TC” means Test case

Example:BRD : BR.1.2. Direct Telesales Consultant shall be able to create and submit application using Jetix Application Form. The purpose is to fill in data and submit eligible application to enable granting decision. Application shall not be eligible for submitting if the mandatory fields (1, 2, 3) are not filled in.Scenario: Test the possibility to create application in Application Form moduleTest case purpose: Test the possibility of Direct Telesales Consultant to create a JetCredit Plus application

Scenario ID = BR.1.2. + S + 1 = BR.1.2.S1Test case ID = BR.1.2.S1 + TC + 1 = BR.1.2.S1TC1

DefinitionTraceability aims to facilitate the management of the requirements, scenarios and test cases during UATRequirement ID is defined in BRD or FSD and the scenario ID is based on it.Once the scenario ID is defined, it is input for test case ID defining.

Scenario ID Scenario Description Test Case

ID Test Case Purpose Prerequisites Test Steps Expected Result

BR.1.2.S1

Test the possibility to submit eligible application in Application Form module

BR.1.2.S1.TC1

Test the possibility of Direct Telesales Consultant to submit a JetCredit Plus application, with filled fields 1,2,3

1.User account for Direct Telesales Consultant2.Valid EGN

1.Login JetIX as a Direct Telesales Consultant2.Start a new JCP application3. Fill-in fields 1, 2, 34. Submit JCP application

The user shall be able to submit a JetCredit Plus application with filled fields 1, 2, 3

19

Scenario ID:It should be simple and easy for tracking. For each business requirement it should exists at least one test scenario.

Test case ID:This is the unique number of each test case, formed from the business requirement number and scenario ID.

Scenario description:Describe shortly the scenario, generated in Step-3

Test steps:What exactly shall be done by whom, where and in what sequence in order to meet the expected result

Prerequisites:What is necessary and has to be done before test case execution. It could be a user account, specific credit, etc…

Test case purpose:Describe the specific business situation, purpose of the test case, defined in Step-4.

Expected result:What is the expected result by user point of view in order to accept the test case result

STEP 7: DESIGN TEST CASES


FROM BUSINESS REQUIREMENT TO TEST CASES

Practical exercise


Business Requirement 1. Автоматично попълващи се полета при задаване на определени критерии

ANALYZE BUSINESS REQUIREMENT

Requirement ID Functionalities Fields Positions Systems ControlsLegend:

При попълване на полето ЕГН в SharePoint от попълващия заявката автоматично да се попълват полетата:

• Име на отчетното лице – стойността на полето Име на отчетното лице ще е равна на стойността на поле „Име” от ТРЗ сорса. Форматът е

текстови и съдържанието не може да бъде коригирано нито от попълващия, нито от одобряващите заявката;

• Позиция – полето е текстово и стойността му е равна стойността в полето „На длъжност” от ТРЗ сорса. Полето се попълва автоматично и

съдържанието не може да бъде коригирано нито от попълващия, нито от одобряващите заявката;

• Отдел – полето е текстово и стойността му е равна на стойността в полето „Отдел” от ТРЗ сорса. Полето се попълва автоматично и

съдържанието не може да бъде коригирано нито от попълващия, нито от одобряващите заявката;

• Офис – полето е текстово и стойността му е равна на стойността в полето „Офис/Магазин” от ТРЗ сорса. Полето се попълва автоматично

и съдържанието не може да бъде коригирано нито от попълващия, нито от одобряващите заявката.

Стойностите на изброените по-горе полета ще се извличат от сорс, който ще съдържа информация за отчетното лице съгласно ТРЗ базата и

съответните на конкретно ЕГН стойности.


DESCRIBE THE TEST SCENARIOS

Scenarios by fields:

BR.1S1 Validate the properties of field “Име на отчетното лице“

BR.1S2 Validate the properties of field “Позиция“

BR.1S3 Validate the properties of field “Отдел“

BR.1S4 Validate the properties of field “Офис“

Scenarios by field properties:

BR.1S1 Validate the automatic filling of the fields “Име на отчетното лице“, “Позиция“, “Отдел“, “Офис“

BR.1S2 Validate the content of the fields “Име на отчетното лице“, “Позиция“, “Отдел“, “Офис“

BR.1S3 Validate the controls of the fields “Име на отчетното лице“, “Позиция“, “Отдел“, “Офис“

BR.1S4 Validate the format of the fields “Име на отчетното лице“, “Позиция“, “Отдел“, “Офис“

23

DESCRIBE THE PURPOSE OF THE TEST CASES

BR.1S1 Validate the properties of field “Име на отчетното лице“

BR.1S1TC1 Validate the automatic filling of field “Име на отчетното лице“ upon filling correct EGN in SharePoint – Expense report

BR.1S1TC2 Validate the content of prefilled field “Име на отчетното лице“ in SharePoint – Expense report

BR.1S1TC3 Validate the format of prefilled field “Име на отчетното лице“ in SharePoint – Expense report

BR.1S1TC4 Validate the impossibility to modify the prefilled data in field “Име на отчетното лице“ in SharePoint – Expense report

BR.1S1 Validate the automatic filling of the fields “Име на отчетното лице“, “Позиция“, “Отдел“, “Офис“

BR.1S1TC1 Validate the automatic filling of field “Име на отчетното лице“ upon filling correct EGN in SharePoint – Expense report

BR.1S1TC2 Validate the automatic filling of field “Позиция“ upon filling correct EGN in SharePoint – Expense report

BR.1S1TC3 Validate the automatic filling of field “Отдел“ upon filling correct EGN in SharePoint – Expense report

BR.1S1TC4 Validate the automatic filling of field “Офис“ upon filling correct EGN in SharePoint – Expense report


Scenario ID Scenario Description Test Case ID Test Case Purpose Prerequisites Test Steps Expected ResultScenario ID Scenario Description Test Case ID Test Case Purpose Prerequisites Test Steps Expected Result

BR.1S1Validate the properties of field “Име на отчетното лице“

BR.1S1TC3

Validate the format of prefilled field “Име на отчетното лице“ in SharePoint – Expense report

- EGN from the TRZ source- User account for SharePoint

1.Open SharePoint2.Go to “Отчитане на разходи” – “Отчет за текущи разходи”3.Click button “New”4.Fill in EGN5.Check the format of field

The field should be in text format

BR.1S2

Validate the automatic filling of the fields “Име на отчетното лице“, “Позиция“, “Отдел“, “Офис“

BR.1S2TC2

Validate the automatic filling of field “Позиция“ upon filling correct EGN in SharePoint – Expense report

- EGN from the TRZ source- User account for SharePoint

1.Open SharePoint2.Go to “Отчитане на разходи” – “Отчет за текущи разходи”3.Click button “New”4.Fill in EGN5.Check the automatic filling of the field

The field should be prefilled automatically with the position of the employee in the TRZ source

BR.1S1TC3 Validate the format of prefilled field “Име на отчетното лице“ in SharePoint – Expense report

BR.1S2TC2 Validate the automatic filling of field “Позиция“ upon filling correct EGN in SharePoint – Expense report

TEST CASES

25

PRACTICAL EXERCISE

Show us what you’ve learned!

Instruction:Read the BRD and test cases, following the steps

• Identify concerned functionalities• Identify concerned fields• Identify concerned positions• Identify concerned systems• Identify concerned controls

1. Analyze business requirements

2. Describe the test scenariosIdentify all situations, coming from the real business processes, concerned in the business requirements and group them by a common criteria:• Concerned process• Concerned changes

3. Describe the purpose of the test caseIdentify all specific and unique situations, based on the scenarios and all othercriteria:• Create all possible variations and combinations

between the concerned processes, products, changes, JetIX positions, based on the criteria from the scenario

PRACTICAL EXERCISE (1/3)

4. Design the test cases• Scenario ID• Scenario description• Test case ID• Test case purpose

• Prerequisites• Test data set• Test steps• Expected result

STEP 1: ANALYZE BUSINESS REQUIREMENTS (ANSWERS)


BR.1.2. Ръчно попълващи се полета от служител

Дата на плащане на заявка – Попълва се датата, на която служителят желае да му се плати отчетът. Датата

трябва да има възможност да се попълва ръчно във формат мм/дд/гггг или използвайки календар в Shp.

Датата на плащане трябва да е поне 2 дни след датата на изпращане на заявката (Например: ако датата на

изпращане на заявка е 01.04.2013, най-ранната възможна дата за плащане трябва да е 03.04.2013). В случай,

че това правило не е изпълнено, е необходимо да се появява предупредителен текст: „Датата на плащане

трябва да е поне два дни след датата на изпращане на заявката”. В случай, че правилото, описано в тази част

е изпълнено => продължаване на нормалния процес на изпращане и одобрение на заявка. Полето се

попълва от изпращача на заявката в New form и може да бъде променяно единствено от отдел Clearing в Edit

form.

BR.1.2. Ръчно попълващи се полета от служителДата на плащане на заявка – Попълва се датата, на която служителят желае да му се плати отчетът. Датата трябва да има възможност да се

попълва ръчно във формат мм/дд/гггг или използвайки календар в Shp. Датата на плащане трябва да е поне 2 дни след датата на изпращане на

заявката (Например: ако датата на изпращане на заявка е 01.04.2013, най-ранната възможна дата за плащане трябва да е 03.04.2013). В случай,

че това правило не е изпълнено, е необходимо да се появява предупредителен текст: „Датата на плащане трябва да е поне два дни след датата

на изпращане на заявката”. В случай, че правилото, описано в тази част е изпълнено => продължаване на нормалния процес на изпращане и

одобрение на заявка. Полето се попълва от изпращача на заявката в New form и може да бъде променяно единствено от отдел Clearing в Edit

form.

Scenario ID Scenario Description Test Case ID Test Case Purpose Prerequisites Test Steps Expected Result



BR.1.2.S1Validate the properties of field “Дата на плащане на заявка“

BR.1.2.S1TC1

Validate the possibility to fill in date manually in the field “Дата на плащане на заявка“

EGN of employee from TRZ source

1. Open SharePoint2. Fill in new Expense Report3. Enter date manually in the

field “Дата на плащане на заявка“

It shall be possible to fill in date manually


BR.1.2.S1TC2

Validate the format of the entered date in the field “Дата на плащане на заявка“


1. Open SharePoint2. Fill in new Expense Report3. Enter date manually4. Check the format of the

entered date

The format of the entered date shall be “мм/дд/гггг”


BR.1.2.S1TC3

Validate the possibility to enter date using SharePoint calendar in the field “Дата на плащане на заявка“


1. Open SharePoint2. Fill in new Expense Report3. Enter date using the

SharePoint calendar in the field “Дата на плащане на заявка“

It shall be possible to enter date using SharePoint calendar


BR.1.2.S1TC4

Validate the impossibility to enter date less than two days in future from the date of sending the report


1. Open SharePoint2. Fill in new Expense Report3. Enter date less than 2 days in

future from the date of sending of the report

It shall not be possible to enter date less than 2 days in future after the date of sending of the report

PRACTICAL EXERCISE – MY PROPSAL (1/4)



BR.1.2.S1TC5

Validate the possibility to enter date exactly two days in future from the date of sending the report



future from the date of sending of the report

It shall be possible to enter date 2 days after the date of sending of the report


BR.1.2.S1TC6

Validate the possibility to enter date more than two days in future from the date of sending the report


1. Open SharePoint2. Fill in new Expense Report3. Enter date more than 2 days

in future from the date of sending of the report

It shall be possible to enter date more than 2 days in future after the date of sending of the report


BR.1.2.S1TC7

Validate the impossibility to enter date in the past in the field “Дата на плащане на заявка“


1. Open SharePoint2. Fill in new Expense Report3. Enter date in the past

It shall not be possible to enter date in the past


BR.1.2.S1TC8

Validate the availability of warning message in case of entered date less than 2 days in future after the date of sending the report



future4. Check availability of warning

message

A warning message: „Датата на плащане трябва да е поне два дни след датата на изпращане на заявката” shall appear.




BR.1.2.S1TC9

Validate the availability of warning message in case of entered date for payment in the past


1. Open SharePoint2. Fill in new Expense Report3. Enter date in the past4. Check availability of warning

message

A warning message: „Датата на плащане трябва да е поне два дни след датата на изпращане на заявката” shall appear.


BR.1.2.S1TC10

Validate the impossibility to edit data in the field “Дата на плащане на заявка“ of sent report by the sender


1. Open SharePoint2. Fill in new Expense Report in

“New form”3. Send the report4. Try to edit the report

The sender shall not be able to edit the data, entered in field “Дата на плащане на заявка“ after sending the report


BR.1.2.S1TC11

Validate the availability of button “Edit Form” in SharePoint in the sent Expense report


1. Open SharePoint as Clearing Specialist

2. Go to sent Expenses reports3. Find the sent report4. Check availability of button

“Edit Form”

Button “Edit Form” shall be available in SharePoint in the sent Expense report


BR.1.2.S1TC12

Validate the possibility to edit data in the field “Дата на плащане на заявка“ by Clearing Specialist


1. Open SharePoint as Clearing Specialist

2. Go to sent Expenses reports3. Find the sent report4. Click button “Edit Form”5. Edit the data in the form

Clearing Specialist shall be able to edit the data in the field “Дата на плащане на заявка“ after sending the report




BR.1.2.S1TC13

Validate the possibility to send Expense report when the field “Дата на плащане на заявка“Is filled correctly


1. Open SharePoint2. Fill in new Expense Report3. Enter correct date4. Send the Expense report

The Expense report shall be sent


BR.1.2.S1TC14

Validate the possibility to approve Expense report when the field “Дата на плащане на заявка“Is filled correctly

Sent Expense report

1. Open SharePoint2. Open sent Expense report3. Approve Expense report

The Expense report shall be approved


STEP 1: ANALYZE BUSINESS REQUIREMENTS (ANSWERS)


BR.2. Визуализация на формата на отчет за текущи разходи

Колоните „Начин на плащане на документ” и „Номер на кредитна карта” и полето „Сума, платена с кредитна

карта” е необходимо да са видими при попълване, преглед и принтиране единствено и само при заявки за

ЕГН-тата, притежатели на кредитни карти, съгласно сорс за кредитни карти. Във всички останали случаи е

необходимо полето „Сума, платена с кредитна карта” да не се появява, а в логиката на всички формули да

придобива стойност 0,00 лв, а под поле „Вид разход” и „Стойност на поле вид разход” и над табличната част с

информация за документа, който се отчита, да се появяват две фиксирани полета:

„Начин на плащане”; „В брой” (стойността на полето „Начин на плащане”)

BR.2. Визуализация на формата на отчет за текущи разходиКолоните „Начин на плащане на документ” и „Номер на кредитна карта” и полето „Сума, платена с кредитна карта” е необходимо да са видими

при попълване, преглед и принтиране единствено и само при заявки за ЕГН-тата, притежатели на кредитни карти, съгласно сорс за кредитни

карти. Във всички останали случаи е необходимо полето „Сума, платена с кредитна карта” да не се появява, а в логиката на всички формули да

придобива стойност 0,00 лв, а под поле „Вид разход” и „Стойност на поле вид разход” и над табличната част с информация за документа, който

се отчита, да се появяват две фиксирани полета:

„Начин на плащане”; „В брой” (стойността на полето „Начин на плащане”)


PRACTICAL EXERCISE – ADDITIONAL (1/2)


PRACTICAL EXERCISE – ADDITIONAL (2/2)


BR.2.S1

Validate the visualization of column „Начин на плащане на документ” when eligible EGN is entered

BR.2.S1TC1

Validate the visualization of column „Начин на плащане на документ” in case of filling in a new Expense report of eligible EGN

Credit card holder’s EGN from TRZ source

1.Open SharePoint2.Go to “Отчитане на разходи” – “Отчет за текущи разходи”3.Click button “New”4.Fill in EGN5.Check visualization of column

The column shall be visible

BR.2.S1


BR.2.S1TC2

Validate the visualization of column „Начин на плащане на документ” in case of reviewing of Expense report of eligible EGN


1.Open SharePoint2.Go to “Отчитане на разходи” – “Отчет за текущи разходи”3.Select the created report4.Click button “Review”5.Check visualization of column


BR.2.S1


BR.2.S1TC3

Validate the visualization of column „Начин на плащане на документ” in case of printing of Expense report of eligible EGN


1.Open SharePoint2.Go to “Отчитане на разходи” – “Отчет за текущи разходи”3.Select the approved report4.Click button “Print”5.Check visualization of column


BR.2.S2

Validate the unavailability of column „Начин на плащане на документ” when ineligible EGN is entered

BR.2.S2TC1

Validate the unavailability of column „Начин на плащане на документ” in case of filling in a new Expense report of EGN without credit card

EGN from TRZ source without credit card

1.Open SharePoint2.Go to “Отчитане на разходи” – “Отчет за текущи разходи”3.Click button “New”4.Fill in EGN5.Check unavailability of column

The column shall not be visible

PRACTICAL EXERCISE (ADDITIONAL) – MY PROPOSAL (1/3)


BR.2.S2


BR.2.S2TC2

Validate the unavailability of column „Начин на плащане на документ” in case of reviewing of Expense report of EGN without credit card




BR.2.S2


BR.2.S2TC3

Validate the unavailability of column „Начин на плащане на документ” in case of printing of Expense report of EGN without credit card




BR.2.S2


BR.2.S2TC4

Validate the unavailability of column „Начин на плащане на документ” in case of filling in new Expense report of EGN with deactivated credit card

EGN from TRZ source with deactivated credit card



BR.2.S2


BR.2.S2TC5

Validate the unavailability of column „Начин на плащане на документ” in case of reviewing of Expense report of EGN with deactivated credit card

EGN from TRZ source with deactivated credit card





BR.2.S3Validate the visualization of two additional fields in case of EGN without credit card is entered

BR.2.S3TC1

Validate the visualization of additional field „Начин на плащане” in case of filling in new Expenses report for EGN without credit card


1.Open SharePoint2.Go to “Отчитане на разходи” – “Отчет за текущи разходи”3.Click button “New”4.Fill in EGN without credit card5.Check availability of the field

The new field shall be available


BR.2.S3TC2

Validate the visualization of additional field „В брой” in case of filling in new Expenses report for EGN without credit card





BR.2.S3TC3

Validate the visualization of additional field „Начин на плащане” in case of reviewing Expenses report for EGN without credit card





BR.2.S3TC4

Validate the visualization of additional field „В брой” in case of reviewing Expenses report for EGN without credit card





user acceptance testing

Documents

regression testregression

test cases

test scenarios

test log

nonregression test purpose

uatuser acceptance test

new functionalities

new software bugs