Index: doc/LaTeX/D-Soil Model - Test report/pictures/TestCoverageForms1.png =================================================================== diff -u -r264 -r728 Binary files differ Index: doc/LaTeX/D-Soil Model - Test report/pictures/TestCoverageForms2.png =================================================================== diff -u -r264 -r728 Binary files differ Index: doc/LaTeX/D-Soil Model - Test report/pictures/TestCoverageData.png =================================================================== diff -u -r264 -r728 Binary files differ Index: doc/LaTeX/D-Soil Model - Test report/D-Soil Model - Test Report.tex =================================================================== diff -u -r700 -r728 --- doc/LaTeX/D-Soil Model - Test report/D-Soil Model - Test Report.tex (.../D-Soil Model - Test Report.tex) (revision 700) +++ doc/LaTeX/D-Soil Model - Test report/D-Soil Model - Test Report.tex (.../D-Soil Model - Test Report.tex) (revision 728) @@ -56,22 +56,22 @@ %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \newcommand{\VersionNumberPlusSpace}{\VersionNumber\xspace} -\newcommand{\VersionNumber}{16.1.3.xxx} +\newcommand{\VersionNumber}{16.1.3.718} \newcommand{\VersionDSLCore}{16.1.3.1188} \newcommand{\VersionDSLFormsGeo}{16.1.3.1236} -\newcommand{\VersionDSLFormsMap}{16.1.3.1237} -\newcommand{\VersionDSLFormsStandard}{16.1.3.1233} -\newcommand{\VersionDSLGeo}{16.1.3.1227} +\newcommand{\VersionDSLFormsMap}{16.1.3.1326} +\newcommand{\VersionDSLFormsStandard}{16.1.3.1321} +\newcommand{\VersionDSLGeo}{16.1.3.1301} \newcommand{\VersionDSLGeographic}{16.1.3.1207} -\newcommand{\VersionDSLGeoIO}{16.1.3.1230} +\newcommand{\VersionDSLGeoIO}{16.1.3.1313} \newcommand{\VersionDSLProba}{16.1.3.1205} \newcommand{\VersionDGSGef}{16.1.1.3} \newcommand{\VersionGefTwee}{3.1.2.1002} \newcommand{\VersionDevExpress}{12.2.13.0} \newcommand{\VersionDotSpatial}{1.8.0.0} \newcommand{\DirectoyPDFTestDocument}{../../../test/DSoilModel-TestDocumenten} -\newcommand{\FileNamePDFTestDocument}{Testdocument_DSoilModel_16_1_3_xxx.pdf} +\newcommand{\FileNamePDFTestDocument}{Testdocument_DSoilModel_16_1_3_718.pdf} @@ -89,12 +89,13 @@ \keywords{WTI2017, Stochastic subsoil schematization, soil profile, soil properties, macro stability, piping, flow slide} -\references{Refer to \autoref{chp:References}.} +%\references{Refer to \autoref{chp:References}.} +\references{} -\summary{This document contains the test report for \ProgramNamePlusSpace \VersionNumber. All the unit tests performed for the validation of \ProgramNamePlusSpace pass and cover 67.3\% of the code, so more than the minimum required code coverage of 60\%. All the features of \ProgramNamePlusSpace were tested during the user interface testing (using test scripts) and work as expected. All the `must-have' and `non-functional' requirements are implemented and met. The functioning of \ProgramNamePlusSpace as described in the Functional Design is therefore ensured. +\summary{This document contains the test report for \ProgramNamePlusSpace \VersionNumber. All the unit tests performed for the validation of \ProgramNamePlusSpace pass and cover 67.4\% of the code, so more than the minimum required code coverage of 60\% for Delta Shell Light products. All the features of \ProgramNamePlusSpace were tested during the user interface testing (using test scripts) and work as expected. All the `must-have' and `non-functional' requirements are implemented and met. The functioning of \ProgramNamePlusSpace as described in the Functional Design is therefore ensured. \textbf{\footnotesize{Samenvatting}} \newline -Dit document bevat het test rapport voor \ProgramNamePlusSpace \VersionNumber. Alle uitgevoerde 'unit tests' voor de validatie van \ProgramNamePlusSpace slagen en dekken 67.3\% van de code, dus meer dan de minimaal vereiste code dekking van 60\%. Alle functionaliteit van \ProgramNamePlusSpace werd getest tijdens de 'user interface' testen (met behulp van testscripts) en werkt zoals verwacht. Alle `must-have' en `niet-functionele' requirements zijn geimplementeerd en voldoen. De werking van \ProgramName, zoals beschreven in het functioneel ontwerp, is daarom gewaarborgd.} +Dit document bevat het test rapport voor \ProgramNamePlusSpace \VersionNumber. Alle uitgevoerde 'unit tests' voor de validatie van \ProgramNamePlusSpace slagen en dekken 67.4\% van de code, dus meer dan de minimaal vereiste code dekking van 60\% voor DSL producten. Alle functionaliteit van \ProgramNamePlusSpace werd getest tijdens de 'user interface' testen (met behulp van testscripts) en werkt zoals verwacht. Alle `must-have' en `niet-functionele' requirements zijn geimplementeerd en voldoen. De werking van \ProgramName, zoals beschreven in het functioneel ontwerp, is daarom gewaarborgd.} \authori{dr. V. Trompille} \revieweri{dr.ir. J.G. van \newline Putten} @@ -113,7 +114,7 @@ This document contains the Test Report for \ProgramName. -The document will not give any background on the context of the WTI project. For this purpose the reader is referred to the WTI2017 and to its supporting technical reports and their background reports underneath (\autoref{sec:1.3}). +The document will not give any background on the context of the WTI project. For this purpose the reader is referred to the WTI2017 and to its supporting technical reports and their background reports underneath (\autoref{sec:1.2}). This document will not describe how the requirements of the functional design are implemented in the program. @@ -323,13 +324,13 @@ \begin{tabular}{|p{\textwidth-83mm-36pt}|p{23mm}|p{28mm}|p{32mm}|} \hline \rowcolor[gray]{.8} Namespace & \textbf{Class} & \textbf{Method} & \textbf{Statement} \\ \hline Deltares.DSoilModel.Data \newline (see \autoref{fig:TestCoverageData}) & 100\% (10/10) & 87.4\% (125/143) & 82.6\% (848/1027) \\ \hline -Deltares.DSoilModel.Forms \newline (see \autoref{fig:TestCoverageForms}) & 84.4\% (27/32) & 51.4\% (289/562) & 64.1\% (3160/4929) \\ \hline -\textbf{Total} & \textbf{88.1\% (37/42)} & \textbf{58.7\% (414/705)} & \textbf{67.3\% (4008/5956)}\\ \hline +Deltares.DSoilModel.Forms \newline (see \autoref{fig:TestCoverageForms}) & 84.4\% (27/32) & 51.4\% (288/560) & 64.3\% (3158/4910) \\ \hline +\textbf{Total} & \textbf{88.1\% (37/42)} & \textbf{58.7\% (413/703)} & \textbf{67.5\% (4006/5937)}\\ \hline \end{tabular} \end{table} -The code coverage of \ProgramNamePlusSpace (\textbf{67.3\%}) is more than the minimum required code coverage of 60\% prescribed in \cite{OverallTestPlanWTI}. +The code coverage of \ProgramNamePlusSpace (\textbf{67.4\%}) is more than the minimum required code coverage of 60\% prescribed in \cite{OverallTestPlanWTI}. @@ -342,23 +343,15 @@ The test of the \textit{User Interface} has been executed by a tester using \textit{Test Script(s)}. All the \textit{Test Scripts} are part of the \textit{Test Document}, joined in appendix \autoref{app:TestDocument} at the end of this Test Report. -\section{Testing of the functional requirements} +\section{Testing of the 'must-have' functional requirements} -In \autoref{tab:OverviewTests}, the Functional Requirements of \ProgramNamePlusSpace are compared to the user-interface features that were tested. Refer to the Functional Design of \ProgramNamePlusSpace \citep{DSoilModel_FunctionalDesign} for a complete description of the requirements. +In \autoref{tab:OverviewTests}, the 'must-have' functional requirements of \ProgramNamePlusSpace are compared to the user-interface features that were tested. Refer to the Functional Design of \ProgramNamePlusSpace \citep{DSoilModel_FunctionalDesign} for a complete description of the requirements. -Almost all the test scripts pass. However, few discrepancies were found on different levels and reported in the Deltares issue tracker tool called JIRA: -\textcolor[rgb]{1,0,0}{\textbf{TODO : Add definitive list of Known Issues}} - -The errors listed above are absolutely not blocking for the use of \ProgramNamePlusSpace within -WTI 2017. All those issues should be fixed in the next release of the program. - -\textcolor[rgb]{1,0,0}{\textbf{TODO : Complete tables below according to the results of the test-scripts}} - The legend of \autoref{tab:OverviewTests} is: \\ \begin{tabular}{p{\textwidth}} \OK $=$ Test-script passes \\ -\OKbut $=$ Test-script passes, but some dysfunctions were found \\ +\OKbut $=$ Test-script passes, but some inconveniences were found \\ \NotOK $=$ Test-script fails \\ \end{tabular} @@ -378,8 +371,8 @@ & \quad -- characteristic points (CSV files) & 7.07 & \OK \\ & \quad -- segments (CSV files) & 7.08 & \OK \\ & \quad -- segments (shape files) & 7.09 & \OK \\ -& \quad -- CPT's (GEF-CPT files) & 7.10 & \OK \\ -& \quad -- Borings (GEF-Boring files) & 7.11 & \OK \\ \hline +& \quad -- CPT's (GEF-CPT files) & 7.10 & \OKbut \\ +& \quad -- Borings (GEF-Boring files) & 7.11 & \OKbut \\ \hline \textbf{REQ 3.3} & \textbf{Select relevant SOS information for project:} & & \\ & \quad -- selection of segment from a list: & 7.09d & \OK \\ @@ -426,13 +419,12 @@ & & 12.05d & \OK \\ & & 12.05e & \OK \\ & & 12.05f & \OK \\ -& & 12.05q & \NotOK \\ -& & 12.05r & \NotOK \\ \hline +& & 12.05q & \OKbut \\ +& & 12.05r & \OKbut \\ \hline \textbf{REQ 5.2} & \textbf{Supply the subsoil schematisation and parameters for the WTI piping kernel:} & & \\ -& \multicolumn{3}{l|}{\quad -- for soil segments, soil profile schematisation, 1D/2D soil profiles scenario's} \\ -& \multicolumn{3}{l|}{\quad soil layer, see REQ 5.1.} \\ -& \quad -- per soil material, soil properties for failure mechanism piping: & & \\ -& & 12.03a & \OK \\ +& \multicolumn{3}{l|}{\quad -- for soil segments, soil profile schematisation, 1D/2D soil profiles } \\ +& \multicolumn{3}{l|}{\quad scenario's and soil layer, see REQ 5.1.} \\ +& \quad -- per soil material, soil properties for failure mechanism piping: & 12.03a & \OK \\ & & 12.03b & \OK \\ & & 12.03c & \OK \\ & & 12.03d & \OK \\ @@ -449,11 +441,11 @@ & & 12.05j & \OK \\ & & 12.05k & \OK \\ & & 12.05l & \OK \\ -& & 12.05s & \NotOK \\ -& & 12.05t & \NotOK \\ \hline +& & 12.05s & \OKbut \\ +& & 12.05t & \OKbut \\ \hline \textbf{REQ 5.4} & \textbf{All relevant subsoil information} & & \\ -& \multicolumn{3}{l|}{See '\textit{per soil material, soil properties}' in REQ 5.1 for macrostability mechanism} \\ -& \multicolumn{3}{l|}{and REQ 5.2 for piping mechanism. } \\ \hline +& \multicolumn{3}{l|}{See '\textit{per soil material, soil properties}' in REQ 5.1 for macrostability } \\ +& \multicolumn{3}{l|}{mechanism and REQ 5.2 for piping mechanism. } \\ \hline \textbf{REQ 6.1} & \textbf{Stochastic characterization of the variables} & 12.04 & \OK \\ \hline @@ -467,10 +459,10 @@ & & 40.05 & \OK \\ & & 43.05 & \OK \\ \hline -\textbf{REQ 6.4} & \textbf{Definition of the location of the 1D profile for Piping and D-Flow Slide} & 34 & \OK \\ -& & 35.02a & \OK \\ -& & 35.04a & \OK \\ -& & 35.04f & \OK \\ \hline +\textbf{REQ 6.4} & \textbf{Definition of the location of the 1D profile } & 34 & \OK \\ +& \textbf{for Piping and D-Flow Slide} & 35.02a & \OK \\ +& & 35.04a & \OK \\ +& & 35.04f & \OK \\ \hline \textbf{REQ 6.5} & \textbf{Profile properties (i.e. yield stresses)} & 30 & \OK \\ \hline @@ -524,7 +516,7 @@ \textbf{REQ 9.4} & \textbf{Draw 2D geometry so as in D-Geo Stability} & 35.03 & \OK \\ \hline % geometry editor -\textbf{REQ 9.5} & \textbf{Reference lines to draw surface lines on } & 28.03b & \OK \\ % Table >> 2D Profiles +\textbf{REQ 9.5} & \textbf{Reference lines to draw surface lines on } & 28.03b & \OK \\ % Table >> 2D Profiles & \textbf{2D profiles} & 33 & \OK \\ % Eigenschappen - Referentielijn & & 35.02h & \OK \\ % selection and move object & & 34.04a & \OK \\ % Delete reference line @@ -569,37 +561,100 @@ & & 41.03e & \OK \\ & & 41.04 & \OK \\ \hline -\textbf{REQ 9.18(a)} & \textbf{Add another 1D profile to an existing 2D profile} & must-have \\ \hline +\textbf{REQ 9.18(a)} & \textbf{Add another 1D profile to an existing 2D profile} & 35.04e & \OK \\ \hline +\textbf{REQ 9.20} & \textbf{Incorporate settlements underneath an embankment} & 35.03 & \OK \\ \hline -\textbf{REQ 9.20} & \textbf{Incorporate settlements underneath an embankment} & must-have \\ \hline -\textbf{REQ 9.23} & \textbf{Import soil area's and segments} & must-have \\ \hline +\textbf{REQ 9.23} & \textbf{Import soil area's and segments} & 44 & \OK \\ \hline \end{longtable} + + + + +\section{Testing of the 'should-have' functional requirements} + \begin{longtable}{|p{20mm}|p{\textwidth-50mm-48pt}|p{15mm}|p{15mm}|} \caption{Overview of the 'should-have' requirements and their corresponding test-scripts} \label{tab:OverviewTestsShouldHave} \\ \hline -\textbf{REQ} & \textbf{Description} & \multicolumn{2}{c|}{\textbf{Test script(s)}} \\ -& & \multicolumn{2}{c|}{\textbf{in appendix \autoref{app:TestDocument}}} \\ \cline{3-4} -& & \textbf{nr.} & \textbf{Status} \\ \hline -REQ 3.2 & Import and view all SOS data & \multicolumn{2}{c|}{Same test-scripts as REQ 3.1} \\ \hline -REQ 3.4 & Import relevant reference data & should-have \\ \hline -REQ 7.2 & Allocation of CPT's and boreholes to a segment & should-have \\ \hline -REQ 7.3 & Overview of all available borings and CPT's in a segment or cross section & should-have \\ \hline -REQ 7.4 & Overview of all available SOS scenario's in a segment & should-have \\ \hline -REQ 8.7 & Show all soil investigation with labels in map view & should-have \\ \hline -REQ 8.8 & Visualize the surface lines with their characteristic points & should-have \\ \hline -REQ 8.12 & Show data from AHN or a WMS server, or other shape files & should-have \\ \hline -REQ 8.14 & Draw SOS profiles in one segment on the same height for comparison & should-have \\ \hline -REQ 8.15 & Show ground investigation simultaneously to REQ 39 at the same reference level & should-have \\ \hline -REQ 8.16 & Compatibility between different views & should-have \\ \hline -REQ 8.17 & Visibility of yield stress & should-have \\ \hline -REQ 9.11 & Copy/ paste segments for one failure mechanism to the next & should-have \\ \hline -REQ 9.21 & Visualize minimum and maximum of layer boundaries from the SOS data & should-have \\ \hline -REQ 9.24 & Table import/export & should-have \\ \hline +\rowcolor[gray]{.8} \textbf{REQ} & \textbf{Description} & \multicolumn{2}{c|}{\textbf{Test script(s)}} \\ +\rowcolor[gray]{.8} & & \multicolumn{2}{c|}{\textbf{in appendix \autoref{app:TestDocument}}} \\ \cline{3-4} +\rowcolor[gray]{.8} & & \textbf{nr.} & \textbf{Status} \\ \hline + +\textbf{REQ 3.2} & \textbf{Import and view all SOS data} & \multicolumn{2}{l|}{Idem as REQ 3.1} \\ \hline + +\textbf{REQ 3.4} & \textbf{Import relevant reference data:} & & \\ +& \quad -- Surface lines & 7.06 & \OK \\ +& \quad -- Characteristic points & 7.07 & \OK \\ +& \quad -- Outside water level & \multicolumn{2}{l|}{not implemented} \\ +& \quad -- PL-lines & \multicolumn{2}{l|}{not implemented} \\ +& \quad -- Polder water level & \multicolumn{2}{l|}{not implemented} \\ \hline + +\textbf{REQ 7.2} & \textbf{Allocation of CPT's and boreholes to } & 42.04c & \OK \\ +& \textbf{a segment } & 42.04d & \OK \\ +& & 43.04d & \OK \\ \hline % Koppel aan dichtsbijzijnde ondergrondsegment + +\textbf{REQ 7.3} & \textbf{Overview of all available borings and CPT's} & 44.01 & \OK \\ +& \textbf{in a segment or cross section} & 44.02 & \OK \\ \hline + +\textbf{REQ 7.4} & \textbf{Overview of all available SOS scenario's } & 44.03 & \OK \\ +& \textbf{in a segment} & 44.04 & \OK \\ \hline + +\textbf{REQ 8.7} & \textbf{Show all soil investigation with labels in } & 43.01 & \OK \\ +& \textbf{map view} & 43.02 & \OK \\ \hline + +\textbf{REQ 8.8} & \textbf{Visualize the surface lines with their characteristic points} & 7.07d & \OK \\\ +& View surface lines with characteristic points on top of a 2D profile & \multicolumn{2}{l|}{not implemented} \\ \hline + +\textbf{REQ 8.12} & \textbf{Show data from :} & & \\ +& -- \quad AHN or a WMS server & \multicolumn{2}{l|}{not implemented} \\ +& -- \quad or other shape files & 7.09 & \OK \\ \hline + +\textbf{REQ 8.14} & \textbf{Draw SOS profiles in one segment on the same height for comparison} & 42.02 & \OK \\ \hline + +\textbf{REQ 8.15} & Show ground investigation simultaneously & 26.03c & \OK \\ +& \textbf{to REQ 39 at the same reference level} & 26.03d & \OK \\ +& & 44.03 & \OK \\ \hline + +\textbf{REQ 8.16} & \textbf{Compatibility between different views} & 45 & \OK \\ \hline + +\textbf{REQ 8.17} & \textbf{Visibility of yield stress} & 30. 03 & \OK \\ \hline + +\textbf{REQ 9.11} & \textbf{Copy/ paste segments for one failure mechanism to the next} & 40.01c & \OK \\ +& & 40.01d & \OK \\ \hline + +\textbf{REQ 9.21} & \textbf{Visualize minimum and maximum of layer boundaries from the SOS data} & 42.06 & \OK \\ \hline + +\textbf{REQ 9.24} & \textbf{Table import/export} & & \\ +& \quad -- Validation messages (export) & 4.02b & \OK \\ +& \quad -- Log messages (export) & 5.02e & \OK \\ +& \quad -- Materials (import) & 12.01d & \OK \\ +& \quad -- Materials (export) & 12.01g & \OK \\ +& \quad -- 1D Profile (import) & 23.01d & \OK \\ +& \quad -- 1D Profile (export) & 23.01g & \OK \\ +& \quad -- 1D Layers (import) & 24.04d & \OK \\ +& \quad -- 1D Layers (export) & 24.04g & \OKbut \\ +& \quad -- 2D Profile (import) & 28.01d & \OK \\ +& \quad -- 2D Profile (export) & 28.01g & \OK \\ +& \quad -- Yield stresses (import) & 30.01d & \OK \\ +& \quad -- Yield stresses (export) & 30.01g & \OK \\ +& \quad -- Geometry point (import) & 31.05b & \OK \\ +& \quad -- Geometry point (export) & 31.05e & \OK \\ +& \quad -- List of surface lines (import) & 36.01d & \OK \\ +& \quad -- List of surface lines (export) & 36.01f & \OK \\ +& \quad -- Surface line (export) & 37.02f & \OK \\ +& \quad -- List of segments (import) & 40.01d & \OK \\ +& \quad -- List of segments (export) & 40.01g & \OK \\ +& \quad -- Stochastic soil profiles (import) & 41.03d & \OK \\ +& \quad -- Stochastic soil profiles (export) & 41.03g & \OK \\ +& \quad -- CPTs for this segment (export) & 41.07g & \OK \\ +& \quad -- Borings for this segment (export) & 41.09g & \OK \\ \hline \end{longtable} + +\section{Testing of the 'nice-to-have' functional requirements} + The nice-to-have requirements listed in \autoref{tab:REQs} are not implemented, so can't be tested. @@ -616,29 +671,63 @@ \textbf{R13} & \textbf{Perform test according to engagement} & A test plan explaining how the program should be tested is available \citep{DSoilModel_TestPlan} and this document (Test Report) shows that all the functionalities of the program are implemented and tested. & \quad \quad \OK \\ \hline \textbf{U124} & \textbf{No crash} & Test-script nr. 47 of the Test Document (see appendix \autoref{app:TestDocument}) attests that no crash occured when performing all test-scripts listed in the Test Document (which represents about 8 hours working with \ProgramName), proving that this requirement is met. & \quad \quad \OK \\ \hline \textbf{U131} & \textbf{Unit tests} & See \autoref{sec:2.1} for an overview of the unit tests. & \quad \quad \OK \\ \hline -\textbf{U133} & \textbf{UI (incl. messages) in Dutch language} & All the test-scripts of the Test Document (see appendix \autoref{app:TestDocument}) checks that the name, hint and unit of each UI field and also all validation and log messages are in Dutch. Only few missing translation was found in test-scripts ?? & \quad \quad \OK \\ \hline +\textbf{U133} & \textbf{UI (incl. messages) in Dutch language} & All the test-scripts of the Test Document (see appendix \autoref{app:TestDocument}) checks that the name, hint and unit of each UI field and also all validation and log messages are in Dutch. Only few missing translation was found in some test-scripts. & \quad \quad \OK \\ \hline \end{tabular} \end{table} +\section{Conclusion} +All the '\textit{must-have}' requirements have been implemented. +Almost all the '\textit{should-have}' requirements are implemented except three of them which are only partly implemented(\autoref{tab:OverviewTestsShouldHave}): +\begin{itemize} + \item \textbf{\textsl{REQ 3.4}}: Outside water level, PL-lines and Polder water level are not available in \ProgramName + \item \textbf{\textit{REQ 8.8}}: It is not possible to view surface lines with characteristic points on top of a 2D profile + \item \textbf{\textit{REQ 8.12}}: Segment shapes from AHN or a WMS server can't be imported in \ProgramName. The user must convert them into shapes files to be able to import them. +\end{itemize} +All the non-functional requirements are met (\autoref{tab:OverviewTestsNF}). + +All the test scripts pass. However, few discrepancies were found on different levels and reported in the Deltares issue tracker tool called JIRA: +\begin{itemize} + \item \href{https://issuetracker.deltares.nl/browse/DSB-684}{DSB-684}: The Warning message in dialog 'Herstel Alles' is not completely correct; + \item \href{https://issuetracker.deltares.nl/browse/DSB-698}{DSB-698}: Log table - Paste and Edit button are available but should not + \item \href{https://issuetracker.deltares.nl/browse/DSB-755}{DSB-755}: Import D-GeoStability STI files: for materials with a default shear strength, the shear strength model after importation is always 'Geen' + \item \href{https://issuetracker.deltares.nl/browse/DSB-601}{DSB-601}: After import of a GEF-CPT file, the imported information is not always correct or relevant + \item \href{https://issuetracker.deltares.nl/browse/DSB-604}{DSB-604}: After import of a GEF-Boring file, the imported information is not always correct or relevant + \item \href{https://issuetracker.deltares.nl/browse/DSB-569}{DSB-569}: The visibility of parameters POP, S and m should depends on the shear strength model + \item \href{https://issuetracker.deltares.nl/browse/DSB-729}{DSB-729}: Min and Max values of some parameters are not in accordance with FO + \item \href{https://issuetracker.deltares.nl/browse/DSB-652}{DSB-652}: In Materials table, the number of decimals of the different parameters is inconsistent + \item \href{https://issuetracker.deltares.nl/browse/DSB-694}{DSB-694}: In Materials table, only the first stochast (Unstaured unit weight) has hints (for Mean, Std deviation....) but not the others stochast + \item \href{https://issuetracker.deltares.nl/browse/DSB-693}{DSB-693}: The choice between ``Geen, Piping and Stabiliteit'' in the faalmechanisme filter of toolbar should not have an influence on the Material filter + \item \href{https://issuetracker.deltares.nl/browse/DSB-683}{DSB-683}: Show legend of CPT cross section + \item \href{https://issuetracker.deltares.nl/browse/DSB-735}{DSB-735}: 1D-Profile - Property window: when table ``Lagen'' is exported, 'Is Aquifer' is not correctly translated + \item \href{https://issuetracker.deltares.nl/browse/DSB-744}{DSB-744}: Missing (or not translated) hints + \item \href{https://issuetracker.deltares.nl/browse/DSB-713}{DSB-713}: Eigenschappen - Hoogtegeometrie: unit of Z should be [m NAP] not [m] + \item \href{https://issuetracker.deltares.nl/browse/DSB-611}{DSB-611}: Missing translations for a number of labels + \item \href{https://issuetracker.deltares.nl/browse/DSB-675}{DSB-675}: When Tabellen-Segmenten and Dwarsdoorsnede windows are combined, the content of the right-hand mouse options menu is incorrect +\end{itemize} + + + +The errors listed above are absolutely not blocking for the use of \ProgramNamePlusSpace within +WTI 2017. All those issues should be fixed in the next release of the program. + + + + %------------------------------------------------------------------------------ \chapter{Conclusion} \renewcommand{\arraystretch}{1.2} -All the unit and integration tests performed for the validation of \ProgramNamePlusSpace pass and cover 67\% of the code, so more than the minimum required code coverage of 60\% prescribed in \cite{OverallTestPlanWTI}. +All the unit and integration tests performed for the validation of \ProgramNamePlusSpace pass and cover 67.4\% of the code, so more than the minimum required code coverage of 60\% prescribed in \cite{OverallTestPlanWTI}. -A complete test of the User Interface has been performed by means of test scripts (see appendix \autoref{app:TestDocument}). Almost all of the test scripts pass; however, a few minor discrepancies were found, such as: \\ -\begin{tabular}{ll} -& -- missing Dutch translation for the hint of some fields \\ -& -- incorrect unit \\ -& -- malfunctioning of some filters \\ -\end{tabular} \\ +A complete test of the User Interface has been performed by means of test scripts (see appendix \autoref{app:TestDocument}). Almost all of the test scripts pass; however, a few minor inconveniences were found and reported in the \textit{Known Issues} list. + However, the discrepancies listed above are not blocking for the use of \ProgramNamePlusSpace version \VersionNumberPlusSpace within WTI 2017, and will be reported in the list of \textit{Known Issues} delivered with the application. -All the '\textit{must-have}' functional requirements and non-functional requirements listed in the Functional Design of \ProgramNamePlusSpace are implemented and met. Only one of the '\textit{should-have}' requirement is not completely implemented (REQ 8.12 ``\textit{Show data from AHN or a WMS server, or other shape files}''. None of the '\textit{nice-to-have}' requirements is implemented, but this will be done in future development of the application. +All the '\textit{must-have}' functional requirements and non-functional requirements listed in the Functional Design of \ProgramNamePlusSpace are implemented and met. Only three of the '\textit{should-have}' requirements are not completely implemented (REQ 3.4, REQ 8.8 and REQ 8.12). None of the '\textit{nice-to-have}' requirements is implemented, but this will be done in future development of the application. \\ \\ \\ @@ -684,7 +773,7 @@ \centering \includegraphics[width=1.4\textwidth]{pictures/TestCoverageForms1.png} \includegraphics[width=1.4\textwidth]{pictures/TestCoverageForms2.png} - \includegraphics[width=1.4\textwidth]{pictures/TestCoverageForms3.png} +% \includegraphics[width=1.4\textwidth]{pictures/TestCoverageForms3.png} \caption{Overview of the code coverage of Deltares.DSoilModel.Forms} \label{fig:TestCoverageForms} \end{figure} @@ -694,7 +783,7 @@ \chapter{Test Document \ProgramNamePlusSpace } \label{app:TestDocument} -The test-scripts part of the Test Document hereafter have been first performed during the development of \ProgramName, using version 16.1.3.618, so a version prior to version \VersionNumber. Because the test document contains about 1200 questions, more than one day is needed to answer all the questions. By lack of time, only the failing tests (of version 16.1.3.618) were performed with version \VersionNumber. A risk exists therefore that a test-script passing with version 16.1.3.618 does not pass anymore with version \VersionNumber. However such a risk is very low because the program is developed in a continuous integration way, which means that an improvement in a feature leading to a failure of an other feature is immediately detected by the build server (via the unit tests) and therefore fixed by the developer. +The test-scripts part of the Test Document hereafter have been first performed during the development of \ProgramName, using versions 16.1.3.618, 16.1.3.634 and 16.1.3.647 so versions prior to version \VersionNumber. Because the test document contains about 1200 questions, more than one day is needed to answer all the questions. By lack of time, only the failing tests were performed with version \VersionNumber. A risk exists therefore that a test-script passing with previous versions does not pass anymore with version \VersionNumber. However such a risk is very low because the program is developed in a continuous integration way, which means that an improvement in a feature leading to a failure of an other feature is immediately detected by the build server (via the unit tests) and therefore fixed by the developer. \includepdf[pages=1, offset=-20 -20, angle=90]{\DirectoyPDFTestDocument/\FileNamePDFTestDocument} @@ -746,6 +835,7 @@ \includepdf[pages=47, offset=-20mm -20mm, angle=90]{\DirectoyPDFTestDocument/\FileNamePDFTestDocument} \includepdf[pages=48, offset=20mm -20mm, angle=90]{\DirectoyPDFTestDocument/\FileNamePDFTestDocument} \includepdf[pages=49, offset=-20mm -20mm, angle=90]{\DirectoyPDFTestDocument/\FileNamePDFTestDocument} +\includepdf[pages=50, offset=20mm -20mm, angle=90]{\DirectoyPDFTestDocument/\FileNamePDFTestDocument} \end{appendices}