Augurk

Our new Blazor-based UI now has a nice feature page with some new features.

We've released a small update on our previous preview that fixes a couple of issues related to the import feature. This should work correctly again now.

Changes:

• 3257a6fd2cd24107f61bf7e3d991f680e3815d5c Fixed some issues with the import feature (#222)
• 8ae1d6221ef6680b1c019943aa704e7c45a0b022 Augurk 3.1.0-Preview-1 (#221)
• d1347a37d23cd8f947e8879de0f17268273ac2d9 Feature/text search (#210)
• cf8054e592c18852d50de750730c9c7442fbe266 Upgrade to .NET Core 3.1 (#201)

This list of changes was auto generated.

It has taken quite some time, but it is finally here! Augurk 3.1.0 Preview-1!
Preview? Yes, we have decided that due to our irregular schedules, from now on we will release parts of new features as soon as they are available and can be used with a reasonable stability.

For now, Augurk will run in a hybrid mode, where you can use both the original (AngularJS) UI, as well as the new features in our up-and-coming (WebAssembly) UI! While this is far from ideal, we believe it is the best approach to give you access to our newest features as soon as possible, without the need to build them in the original UI as well.

Changes in this preview:

• Reduced storage 
We reduced the amount of storage required for your features by combining unchanged versions, without losing any actual data.
• Preview button 
A preview button has been added to the top right of the original UI, leading you to the preview functionality.
• Text search 
From the preview UI, it is now possible to perform a full text search on all your features. At this moment the search results only contain features which contain a complete match for the provided word. As of yet, search for partial words is not yet supported. 
For now, the results will link to the features in the original UI.

Naturally, changing the data structure also broke some features. While we fully intend to fix this before going stable with 3.1.0, these features are not available in Preview-1

• Data retention 
Preview-1 will not apply data retention and will also not retain the upload date of newly uploaded futures for future retention. We will think of a fitting solution for the features which were uploaded using this version in the stable version
• Feature dependencies 
Feature dependencies other than the @parentFeature-tag will not display properly, as the current implementation is version-bound. We will have to redesign the storage for this feature from scratch
• Test results 
While test results can still be uploaded and linked to your scenario’s, they will now be linked to all identical version of the tested feature instead of only to the provided version.

So, quite some changes, and we are far from done. We certainly hope to provide more functionality in the new UI, as well as fix the broken features listed above.
Until that time, we are happy to receive your feedback regarding this preview. Do not hesitate to share any feedback, be it a new thought you have or issues you encounter, through our issue tracker. Until the next version!

Mark & Jonathan

Changes:

• 8ae1d6221ef6680b1c019943aa704e7c45a0b022 Augurk 3.1.0-Preview-1 (#221)
• d1347a37d23cd8f947e8879de0f17268273ac2d9 Feature/text search (#210)
• cf8054e592c18852d50de750730c9c7442fbe266 Upgrade to .NET Core 3.1 (#201)

This list of changes was auto generated.

Changes:

• bbc56bd56dd27933cf02685643ae58897dd429c5 Augurk 3.0 (#98)

This list of changes was auto generated.

Sequence diagrams and import/export

In this release we've added two new features:

• Support for sequence diagrams (resolves #76)
• Import/export feature so that data in Augurk can be backed up or moved between instances (resolves #77)

We've also fixed the following bug:

• Tag search didn't work anymore (fixes #70)

This release lays the groundwork for a larger feature called "dependency visualizer". It will eventually allow users to visualize dependencies between features automatically based on static analysis. In this version the API's were added to Augurk to allow uploading and subsequently retrieving this data.

Additionally the following minor fixes have gone into this release:

• Added API documentation using Swagger
• Implemented separate scrollbars for the menu and the current feature file
• Some minor textual fixes to the UI
• Added publish profile for publishing to an Azure WebApp

This release fixes an issue that occurred with 2.5.0 for brand new installations. If you're having problems installing Augurk with 2.5.0, please try again with this version. If 2.5.0 is working just fine for you, you can skip this version.

Thanks to @GijsVanDulmen for reporting the issue.

From now on Augurk supports an expiration period for features which' version matches specified criteria.
This new option can be configured on the new configuration page.
Additionally, the configuration page also allows you to customize the name of your instance!

Augurk now supports the concept of product descriptions. These descriptions will be shown on the product page where originally the homepage was shown.

This serves as the initial implementation for Product Landing Pages. In the future internal editting options are desired.

Descriptions can be uploaded via the Augurk Commandline Tool from version 3.1.0 onward.

Fixes #26.

If you use the commandline tool through augurk publish and do not specify a version a version number of 0.0.0 is implied. Augurk already suppresses the version dropdown altogether if the only version available is 0.0.0.

Augurk itself is not updated, please refer to version 2.2.0 for deployable binaries.

Implemented support for providing authentication when using the commandline tool.
Both IntegratedSecurity and BasicAuthentication are now available.

Naturally, this will only work when also configured for Augurk (manually).

With thanks to @roycornelissen

N.B.
Augurk itself is not updated, please refer to version 2.2.0 for deployable binaries

The commandline tool now supports wildcards while using the upload functionality.
You can use ? to replace a single character or ***** to replace any number of them.
Additionally, it is now possible to only supply a folder name to upload all contained .feature files.

Due to a merge error, an incorrect ordering was left behind in the code. This resulted in some features not being displayed. This issue has been resolved.

This version resolves some nuisances to our users:

• Products (formerly: branches) are now sorted by name
• Features, Groups and Product can now be deleted from our commandline tool
• Specific versions of features can be deleted from our commandline tool

Added Support for Semantic Versioning
Removed some minor nuisances