StructuralAnalysisFormat.Tests.Infrastructure
1.7.3-alpha00001
dotnet add package StructuralAnalysisFormat.Tests.Infrastructure --version 1.7.3-alpha00001
NuGet\Install-Package StructuralAnalysisFormat.Tests.Infrastructure -Version 1.7.3-alpha00001
<PackageReference Include="StructuralAnalysisFormat.Tests.Infrastructure" Version="1.7.3-alpha00001" />
paket add StructuralAnalysisFormat.Tests.Infrastructure --version 1.7.3-alpha00001
#r "nuget: StructuralAnalysisFormat.Tests.Infrastructure, 1.7.3-alpha00001"
// Install StructuralAnalysisFormat.Tests.Infrastructure as a Cake Addin #addin nuget:?package=StructuralAnalysisFormat.Tests.Infrastructure&version=1.7.3-alpha00001&prerelease // Install StructuralAnalysisFormat.Tests.Infrastructure as a Cake Tool #tool nuget:?package=StructuralAnalysisFormat.Tests.Infrastructure&version=1.7.3-alpha00001&prerelease
StructuralAnalysisFormat.Tests.Infrastructure
This package adds some functionality that may come in handy for testing purposes.
Data builders
One of the features are what we call data builders These are fluent-api classes that allow you to quickly construct data objects that by default pass validation. They also have the benefit that if a property would be renamed on an object, the data builder will be adjusted but the API of the builder remains the same. Which means you won't have to make any changes to your test code!
Good to know - Metric & Imperial
Any values unit wise that are set using doubles, will always be metric as this is how the data builders are set up. If the builder accepts actual units, you are free to provide it with units defined in the imperial system for example.
Good to know - Sane values
While we do our best to make sure that the model actually makes sense in the context of structural engineering, this may sometimes not be the case.
So it may happen that some objects constructed by either the data builders or from the house model have weird values that do not make sense to a structural engineer.
Usage
The API is the same for each builder available.
In general (replace <NameOfDataObject> with the name of object):
- The builders all end with *Builder in their name
<NameOfDataObject>Builder.Create();
will quickly create an object using either pre-defined or random values that are considered valid in terms of validation<NameOfDataObject>Builder.Setup();
allows you to enter "configuration" mode for the builder<NameOfDataObject>Builder.Setup() ... .Build();
will construct the object for you using the configured settings you have defined in the...
part
using SAF.Infrastructure.Tests.DataBuilders.StructuralElements;
using SAF.DataAccess.Models.StructuralElements;
// Create a node with zero value coordinates (X,Y,Z)
ExcelStructuralPointConnection node = ExcelStructuralPointConnectionBuilder.Create();
// Create a node with coordinate values, X = 2 meters, Y = 5.5 meters and Z = 7 meters
ExcelStructuralPointConnection node2 = ExcelStructuralPointConnectionBuilder
.Setup()
.WithCoordinates(2D, 5.5D, 7D)
.Build();
Example models
Another feature is that we have included a full-blown house model.
The goal of this model is to include every supported object from the SDK.
You can get this model by executing the following lines of code:
using SAF.Infrastructure.Tests.Models;
using SAF.DataAccess.Models;
House house = new House();
ExcelModel houseAsModel = house.Construct();
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
.NET Core | netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
.NET Standard | netstandard2.0 is compatible. netstandard2.1 was computed. |
.NET Framework | net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
MonoAndroid | monoandroid was computed. |
MonoMac | monomac was computed. |
MonoTouch | monotouch was computed. |
Tizen | tizen40 was computed. tizen60 was computed. |
Xamarin.iOS | xamarinios was computed. |
Xamarin.Mac | xamarinmac was computed. |
Xamarin.TVOS | xamarintvos was computed. |
Xamarin.WatchOS | xamarinwatchos was computed. |
-
.NETStandard 2.0
- StructuralAnalysisFormat (>= 1.7.3-alpha00001)
- UnitsNet (>= 4.72.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated |
---|---|---|
1.7.3-alpha00001 | 70 | 11/8/2024 |
1.7.3-alpha.1 | 41 | 11/8/2024 |
1.7.2 | 154 | 2/20/2024 |
1.7.1 | 301 | 2/14/2023 |
1.7.0 | 281 | 2/10/2023 |
1.6.1 | 270 | 2/7/2023 |
1.6.0 | 297 | 1/30/2023 |
1.5.6 | 345 | 11/21/2022 |
1.5.5 | 400 | 10/10/2022 |
1.5.4 | 462 | 9/22/2022 |
1.5.3 | 424 | 9/20/2022 |
1.5.2 | 419 | 9/16/2022 |
1.5.1 | 446 | 9/7/2022 |
1.5.0 | 432 | 8/26/2022 |
1.4.0 | 436 | 7/29/2022 |
1.3.2 | 444 | 6/10/2022 |