search

Megabit / Blazorise

Blazorise is a component library built on top of Blazor with support for CSS frameworks like Bootstrap, Tailwind, Bulma, AntDesign, and Material.
https://blazorise.com/
Other
3.29k stars 531 forks source link

Helper Packages : Unit Tests #4977

Closed David-Moreira closed 10 months ago

David-Moreira commented 1 year ago

Provide helper packages.

Unit tests has been a recurring topic where users could benefit of a few helper methods to help them get started faster.

@stsrki ideas for the helper packages naming convention? Blazorise.Helpers.BunitTests Blazorise.Utilities.BunitTests Blazorise.BunitTests

stsrki commented 1 year ago

I would go with Tests in the middle in case we in the future add more support for other testing libraries. We could also add an E2E tests.

David-Moreira commented 1 year ago

I would go with Tests in the middle in case we in the future add more support for other testing libraries. We could also add an E2E tests.

  • Blazorise.Tests.bUnit
  • Blazorise.Tests.Playright

But do we make a convention for helper packages? Like Helpers.Tests.bUnit or Utilities.Tests.bUnit

Just so we can clearly separate helper packages from the actual the product packages? or no point? For example I remember us speaking about making some utilities for helping with datagrid, expressions and stuff

stsrki commented 1 year ago

I don't think it is needed to have an extra level of naming. Just go with Blazorise.Tests.{ProviderName}.

David-Moreira commented 1 year ago

Ok, It was just if we had other type of helper packages we would have an easy to go to name, and everything would be under the same bucket. I'm fine with this also.