Business Tests Project

Get Started. It's Free
or sign up with your email address
Business Tests Project by Mind Map: Business Tests Project

1. build process

1.1. move to USAT

1.1.1. get working enterprise service

1.1.2. detailed design

1.1.3. downhload from ftp

1.1.4. checkin

1.2. Closed

1.2.1. update build definition for reporting

1.2.1.1. run tests with all features at once with exporting results

1.2.1.2. generate reports

1.2.1.3. send emails

1.2.1.4. update to nunit3

1.2.1.5. remove old build template

1.2.2. email results for scheduled test runs - WI00117153

1.2.3. upgrade specflow

1.2.3.1. upgrade on test server

1.2.3.2. upgrade on local machine

1.2.3.3. install VS etension if necessary

1.2.3.4. update build definition as necessary

1.2.3.5. regenerate featues files

1.2.3.5.1. update if necessary

1.2.4. test failures on server

1.2.4.1. WPF

1.2.4.1.1. stability issues

1.2.4.2. WEB

1.2.4.2.1. Dashboard - hover over tooltips

1.2.4.2.2. View Booking - Wait until grid loaded then get first cell in SortGridByColumn (actions_helper.js)

1.2.4.2.3. Can't start transport booking after certain failures

1.2.4.3. failures due to enterprise service

1.2.4.3.1. "ExceptionMessage":"The remote certificate is invalid according to the validation procedure."

1.2.5. changes for check in process

1.2.5.1. update PlatformBuilder.VersionControl solution to queue tfs build for business tests

1.2.5.2. change build definition to queue dat build instead of GlowCheckIn

1.2.5.3. send for review

1.2.5.4. checkin

1.2.6. fix server environment

1.2.6.1. bug with CargowiseApplicationLogin user

1.2.6.2. Environemnt Setups

1.2.6.2.1. code base

1.2.6.2.2. portals

1.2.6.2.3. desktop

1.2.6.2.4. configurations

1.2.6.2.5. enterprise service

1.3. Bugs

1.3.1. issue with world constructor

1.3.1.1. check with cucumber ver6.0 (used 5.0)

1.3.2. FIX - checkin comment not taken from test designer

1.4. move to DAT

1.4.1. plan what's needed

1.4.1.1. create a list of software to be installed

1.4.1.2. record all necessary build/execute operations with conditions

1.4.1.3. potential issues

2. Test Snippets

2.1. Update according to current state

2.1.1. wpf tests

2.1.1.1. fixes left todo

2.1.1.1.1. correct featues to use only long column names

2.1.1.1.2. WPF tests unstabe dragNdrop

2.1.1.1.3. WPF tests unstabe more button error

2.1.2. web tests

2.1.2.1. stability issues

2.1.2.1.1. check tooltips of tiles on dashboard

2.1.2.1.2. unstable maintain product

2.2. Update after moving to USAT and getting new scenarios

2.2.1. make possible to add platform builder tests

2.3. detect portal by tag name, and login to appropriate portal - WI00116703

2.3.1. TO VERIFY: can you access tags from scenario with cuke 5.1

2.3.2. need also to launch on all specified portals, not just the one in env.yaml

2.4. Enhancements

2.4.1. + support detect by all short/long column names

2.4.2. add screenshots - WI00117120

2.4.2.1. web - take base64 encoded screenshot on scenario failure

2.4.3. Closed

2.4.3.1. get rid of TestDesigner tests - WI00117103

2.4.3.2. run only the modified/added features when submitting from test designer - WI00117188

2.5. Bugs

2.5.1. Closed

2.5.1.1. platform builder killed after demo script failure - WI00116861

3. Test Designer

3.1. fix existing functionality

3.1.1. verify checking in changes

3.1.2. fix scrollbars

3.2. correct according to change to USAT

3.2.1. detailed design for BT Designer changes

3.3. add link to report summary on TestDesigner - WI00117187

3.4. Running tests on multiple portals -

3.5. Bugs

3.5.1. FIX - make pending tests run form resizable

3.5.2. Closed

3.5.2.1. FIX - error when switching portals - WI00119743

4. Reporting

4.1. ReportUnit (html reports generation tool)

4.1.1. coding

4.1.2. comply with standards - WI00115885

4.1.2.1. unit tests

4.1.2.2. code contracts

4.1.2.3. nuget packages

4.1.2.4. add to source control

4.1.3. Bugs

4.1.3.1. cuke results not searched in subdirectories

4.1.3.2. fails when no steps specified

4.1.4. Enhancements

4.1.4.1. Closed

4.1.4.1.1. append unique ids to report html files to be able to have same report names

4.1.4.1.2. add success/fail to email subject - WI00119253

4.1.4.1.3. add email summary report - WI00119263