When testing arrange, the default behavior is to pull the last column of the data.frame in question (since arrange does not modify columns like a mutate would). This can have problems with testing since the level of uniqueness of the sort is important to test success / failure.
Further, there can be problems with adding mutate() to create the column so the same level of uniqueness is present because
it is not a unit test of arrange
some verbs (like desc(column)) are not valid within mutate
Very tricky... it almost seems we need a "unique value" column like id or something... and then every arrange needs to be done by the computation in question and then by the unique column.
Relates to #8
When testing
arrange, the default behavior is topullthe last column of the data.frame in question (sincearrangedoes not modify columns like amutatewould). This can have problems with testing since the level of uniqueness of the sort is important to test success / failure.Further, there can be problems with adding
mutate()to create the column so the same level of uniqueness is present becausearrangedesc(column)) are not valid withinmutateVery tricky... it almost seems we need a "unique value" column like
idor something... and then every arrange needs to be done by the computation in question and then by the unique column.