Comments (4)
OR13
commented on July 17, 2024
@msporny Similar reasoning for assigning you this as we had for #49... make sure to delegate if its not achievable.
from did-test-suite.
peacekeeper
commented on July 17, 2024
+1 to creating a separate suite for each major section.
from did-test-suite.
msporny
commented on July 17, 2024
I have raised PR #52 to do this. Please review and see if the refactoring works for everyone. It's not entirely split on section... some of the stuff was dicey, like the metadata structure... but the rest is split on section.
from did-test-suite.
iherman
commented on July 17, 2024
The issue was discussed in a meeting on 2021-04-06
- no resolutions were taken
View the transcript
7.3. Proposal to create a suite per major section of the spec
See github issue did-test-suite#50.
Markus Sabadello: relatively simple
… internal restructuring to organise the test suite into multiple suites which each contain tests related to one section
… in the initial draft of the test suite we had one suite which contained a huge list of tests
… this is a way of dividing and structuring the test suite a bit better
… will result in better reports
Daniel Burnett: also editorial
from did-test-suite.
Related Issues (20)
- universal-resolver-did-ccp not passing test HOT 3
- BLS12381_G2 unsupported from did test suite
- Test server's generate-test won't run HOT 2
- Valid id property value throws in test runs HOT 4
- How should a byte steam be encoded into JSON for a dereferenced Did URL that points to an external resource outside the DID Document? HOT 14
- Consistency on implementation JSON's properties needed for report generation HOT 6
- Hosting of did-test-suite HOT 2
- Scanning of implementation directory and test suites selection HOT 3
- Top level index.html is gone HOT 3
- Type error on endpoint
- Generate report with github pages HOT 4
- Is it possible to change width of the report? HOT 4
- Test Suite reporting broken with removal of Examples implementation HOT 3
- Every commit now results in a CI failure HOT 16
- TypeError: Cannot read property 'ancestorTitles' of undefined HOT 4
- Different test results for test-suite server
- Symbols are confusing HOT 6
- Can we smartly link from the test suite to the registry?
- Add test to check if JSON-LD DID Documents are dropping any terms
- First two Specification Cases
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 did-test-suite.