Authentication strategies
SharePoint client
Samples
Sandbox
Testing
🚦Gosip automated testing
In a clone or fork.
Authentication testing
Create auth credentials store files in
./config folder for corresponding strategies:1
go test ./... -v -race -count=1
Copied!
Not provided auth configs and therefore strategies are ignored and not skipped in tests.
API integration tests
Create auth credentials store files in
./config/integration folder for corresponding environments:- private.spo.json
- private.2013.json // 2013 has its nuances with OData mod and not supported methods
1
SPAUTH_ENVCODE=spo go test ./api/... -v -race -count=1
2
SPAUTH_ENVCODE=2013 go test ./api/... -v -race -count=1
Copied!
API integration tests are mostly targeted to SharePoint Online and not regularly processed on the legacy versions of the platform so you can face some test exceptions which still should be escaped with
t.Skip and envCode != "spo" condition:1
if envCode != "spo" {
2
t.Skip("is not supported with old SharePoint versions")
3
}
Copied!
Environment variables
SPAUTH_ENVCODE=codeenvironment variable switches target environments.spois a default one.SPAPI_HEAVY_TESTS=trueturns on "heavy" methods, e.g. web creation.
Run manual tests
Modify
cmd/test/main.go to include required scenarios and run:1
go run ./cmd/test
Copied!
Optionally, you can provide a strategy to use with a corresponding flag:
1
go run ./cmd/test -strategy adfs
Copied!
Run CI tests
Configure environment variables:
- SPAUTH_SITEURL
- SPAUTH_CLIENTID
- SPAUTH_CLIENTSECRET
- SPAUTH_USERNAME
- SPAUTH_PASSWORD
1
go test ./... -v -race -count=1
2
SPAUTH_ENVCODE=spo SPAPI_HEAVY_TESTS=true go test ./api/... -v -race -count=1
Copied!
Test coverage
Branch
Coverage
Master
Dev
We are targeted to keep code coverage higher than 80% for API and Auth methods altogether.
Last modified 2yr ago
Export as PDF
Copy link