Comments (4)
Gotcha. We would probably just gather and sort the results before doing a should.Resemble
assertion. For now, we don't see a need to add this kind of assertion to the package, but thanks for checking in first.
Did you know that you can implement your own custom assertions? Suppose you implemented a function with a very specific signature:
package yourpackage
func ShouldEqualUnordered(actual interface{}, expected ...interface{}) string {
// your implementation here...
}
Then you can use your custom assertion in a So
call:
So(collectionA, yourpackage.ShouldEqualUnordered, collectionB)
from assertions.
I'm happy to build this myself, but hoping to get approval from a team member before I get started. Lmk!
from assertions.
It has always seemed to me that ordering is a fundamental characteristic of slices and arrays, so an assertion on slices or arrays should require that elements be in a consistent order. Will you please provide examples or code snippets that illustrate your use case more fully?
from assertions.
any code that involves concurrency may append results to an array in different orders each time
from assertions.
Related Issues (20)
- Assertions should allow an optional string with a better message HOT 3
- ShouldEqualJSON only supports JSON Objects at the root HOT 1
- [suggestion] loose slice equality HOT 1
- ShouldBeEmpty should warn if subject has no length
- ShouldEqualJSON does not work with json arrays HOT 4
- Problem running test HOT 1
- httptest.NewServer starts in background goroutine and causes data race when used with shouldNotBeNil (which depends upon string formatting) HOT 3
- Golang 1.16 beta 1: TestMapSortRendering fails on s390x HOT 7
- building error HOT 2
- Drop go1.17 dependency HOT 2
- Super small typo in documentation of ShouldNotBeBlank
- Versioning scheme changed backwards HOT 3
- TestMapSortRendering fails with go1.18 HOT 1
- map[int64]bool ShouldContainKey didn't work as expected HOT 4
- ShouldResemble can fail when there's no visual diff between the inputs HOT 1
- The module declares is incorrect HOT 2
- ShouldEqual no longer works with functions HOT 5
- Major version shall be bumped since v1.51.0 HOT 5
- module declares its path as: github.com/smarty/assertions but was required as: github.com/smartystreets/assertions HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from assertions.