You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Generate a DFS service client when working with Blob as well
* Fix testing, default include directory stubs when sensible
Also removes leftover isHNStoHNS flag from Sync.
* Use HNS acct with BlobFS location
* Adapt to using HNS account instead when using BlobFS
* Fix tests
* Hopefully final test fixes?
* Revert ps cli auth tests
* Accidental leftovers of manual local testing
* Clean up other test reductions
---------
Co-authored-by: Gauri Lamunion <51212198+gapra-msft@users.noreply.github.com>
cooked.isHNSToHNS=true// override HNS settings, since if a user is tx'ing blob->blob and copying permissions, it's DEFINITELY going to be HNS (since perms don't exist w/o HNS).
Copy file name to clipboardexpand all lines: e2etest/declarativeRunner.go
+20-8
Original file line number
Diff line number
Diff line change
@@ -111,16 +111,16 @@ func RunScenarios(
111
111
validateValidate, // TODO: do we really want the test author to have to nominate which validation should happen? Pros: better perf of tests. Cons: they have to tell us, and if they tell us wrong test may not test what they think it tests
112
112
// _ interface{}, // TODO if we want it??, blockBlobsOnly or specific/all blob types
113
113
114
-
// It would be a pain to list out every combo by hand,
115
-
// In addition to the fact that not every credential type is sensible.
116
-
// Thus, the E2E framework takes in a requested set of credential types, and applies them where sensible.
117
-
// This allows you to make tests use OAuth only, SAS only, etc.
114
+
// It would be a pain to list out every combo by hand,
115
+
// In addition to the fact that not every credential type is sensible.
116
+
// Thus, the E2E framework takes in a requested set of credential types, and applies them where sensible.
117
+
// This allows you to make tests use OAuth only, SAS only, etc.
// TODO: do we need something here to explicitly say that we expect success or failure? For now, we are just inferring that from the elements of sourceFiles
123
+
// TODO: do we need something here to explicitly say that we expect success or failure? For now, we are just inferring that from the elements of sourceFiles
for_, v:=rangecommon.AllLinuxProperties { // properties are evaluated elsewhere
738
737
delete(expected, v)
739
-
delete(actual, v)
738
+
delete(cased, v)
740
739
}
741
740
742
-
s.a.Assert(len(actual), equals(), len(expected), "Both should have same number of metadata entries")
743
-
cased:=metadataWithProperCasing(actual)
741
+
s.a.Assert(len(cased), equals(), len(expected), "Both should have same number of metadata entries")
742
+
744
743
forkey:=rangeexpected {
745
744
exValue:=expected[key]
746
745
actualValue, ok:=cased[key]
747
-
s.a.Assert(ok, equals(), true, fmt.Sprintf("expect key '%s' to be found in destination metadata", key))
746
+
s.a.Assert(ok, equals(), true, fmt.Sprintf("%s: expect key '%s' to be found in destination metadata", f.name, key))
748
747
ifok {
749
-
s.a.Assert(exValue, equals(), actualValue, fmt.Sprintf("Expect value for key '%s' to be '%s' but found '%s'", key, *exValue, *actualValue))
748
+
s.a.Assert(exValue, equals(), actualValue, fmt.Sprintf("%s: Expect value for key '%s' to be '%s' but found '%s'", f.name, key, *exValue, *actualValue))
0 commit comments