You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Fail Master Page

This page is created to help fulfilling the role as Fail Master as efficient as possible. As the role of Fail Master shifts from person to person on daily basis, it is important to share information on findings such that for example Work In Progress tests are evaluated multiple times by various people.

Build Server Test Categorization

This list is the aid the current Fail Master in providing an overview of the the tests that have been categorized. It is there to provide an overview of what are issue to be solved by the Fail Master, which failing Work In Progress tests are due to being targets for future features or future improvements, and which are due to bugs.

Test: Name of the test. Formate is <Test Class>.<Test Method>

Reason/Cause for failure or Work In Progress: Provides an explanation why a test is failing or why the test is set as Work In Progress.

Related Issue: If there is an issue related with the failing test.

Associated Developer: Developer associated with this test. <Developer> is used to indicate that this person has created the test. <Developer> is used to indicate the person is assigned with solving the issue.

Freshness Date: Date when this entry was updated

Related Check-in: Which check-in is related to the test. In italic means it might be associated with this commit. In bold means it is certain this check-in is the cause of the failure.

Test

Reason/Cause for failure or Work In Progress

Related Issue (Tools-...)

Associated Developer

Freshness Date

Related Check-in

FunctionFilterTest.FilterUsingMultiComponent

Missing Feature: Support for filtering multi-component

-

-

24 Sept 2010

13596

FunctionTest.EventShouldNotBubbleIfReducedFunctionIsUnaffected

Bug: Event bubbling for filtered functions

-

-

24 Sept 2010

15843

Missing Feature: Precondition for Arguments not implemented

Missing Feature: Precondition for Arguments not implemented

-

bouvrie

24 Sept 2010

17121

FunctionTest.ValuesChangedEventFiredWhileFunctionIsNotConsistent

Bug/Missing Feature: Incorrect updating of Multi-component Function

-

-

24 Sept 2010

17217

TableViewCopyPasteTest.PasteIntoNewRow

Bug: Pasting with Row-Select

3069

-

24 Sept 2010

11269

TableViewTest.AddDataToViewUpdatesDatasource

Bug: Syncing DataBinding does not work properly for TableView

-

witlox

24 Sept 2010

12267

TableViewTest.ComboBoxTypeEditorWithCustomFormatter_ShouldWork_Tools7594

Bug: CustomFormatter on column overrides unspecified TableView CustomFormatter

7594

bouvrie, schre_tn

24 Sept 2010

18999

TableViewTest.TableViewCursorKeysWhileInCellEditModeShouldWorkLikeExcel

Build Server Failure: Hangs on build server

6647

schre_tn

24 Sept 2010

16794

HisFunctionStoreTest.HisFunctionStoreWithNetworkCoverage

Unstable Test: System.IO.IOException : The process cannot access the file 'D:\BuildAgent\DeltaShell\test-data\Plugins\DelftModels\DeltaShell.Plugins.ImportExport.Sobek.Tests\HisData\HisAndNetwork\CALCPNT.HIS' because it is being used by another process.

-

-

24 Sept 2010

-

ProjectQueryContextTest.GetAllByFeatureType_DemoNetwork_CanFindSpecificFeatures

Pending: Test seems OK-ish, maybe implement additional assertions. TODO: Check with hummel if test is ready to be returned from Work In Progress

5920

hummel

24 Sept 2010

-

WaterFlowModelApi1D3DTest.ClearPreviousResultFilesIfNetworkIsInvalid

Unstable Test: Test green for 3 months, put back in Production and then failed.

-

-

24 Sept 2010

-

Test back into production

Some (old) tests have been put in Work In Progress and have been resting here for some time. Some of these tests have proven to succeed consistently for and are potentially ready to be returned in the regular test-environments. These returned tests do need to be monitored closely by the Fail Master in order to be sure that these tests do no turn into "occasionally failing tests", due to various causes such as state-dependency. Any test that has succeeded consistently for 2 weeks in the does not have to be actively monitored any more and can be removed from the following list.

Test

Reason back into production

Check-in

Date back into production

SobekNetworkImporterTest.RunZwolleModelWithAddedCrossSection

Licence problems do not appear to occur any more.

19013

24 Sept 2010

SobekRoughnessImporterTest.ImportReverseRoughness

Probably fixed in revision 13914 and forgot to remove WIP attribute.

19013

24 Sept 2010

PiTimeSeriesLateralSourceImporterTest.ImportSelectedTimeSeriesToLateralSource

Checked code with janse_ma and test is complete. Test never failed.

19013

24 Sept 2010

PiTimeSeriesTargetItemImporterTest. ImportSelectedTimeSeriesToBoundaryCondition

Checked code with janse_ma and test is complete. Test never failed.

19013

24 Sept 2010

WaterFlowModel1DGuiIntegrationTest.DeletingAModelWithNetCDFOutputAfterCreatingANewProjectShouldWork

Checked code with donchyt and test is complete. Forgot to remove Work In Progress Attribute

19013

24 Sept 2010

Open Test Issues

There are a few open issues left to either solve, investigate or monitor. These are listed as follows:

Open ToDo's

Action

Freshness Date

WaterQualityModelFileFactoryTest.WriteLoadsFileForLargeNetwork timing upper limit might need to get increased to about 500, in order to keep the mean at around 75% of this limit.

Monitor (Take action if deemed needed)

24 Sept 2010

The following exception has been popping up (keep in mind that the tmp folder is randomly generated!) :
System.IO.IOException: The process cannot access the file 'D:\BuildAgentTemp\buildTmp\tmp1BC1.tmp\work\sobek.log' because it is being used by another process.
It causes tests to fail randomly at times, such as:

  • WaterFlowModel1DTest.TestSimpleModelWithMultipleCrossSection
  • WaterFlowModel1DSaltTest.TestDispersionParameterSee test (Integration) for failing tests with this signature. The file sobek.log does not always get released either correctly or in time, resulting in state-dependent tests and cause these random failures.

Investigate

24 Sept 2010

  • No labels