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
These test are run by the pipeline but running them locally can be convenient to see issues early or to debug issues seen in the pipeline locally.
47
+
- Run against release configuration by select release configuration at the the top of solution explorer (to check against optimisation such as tree shaking for example)
48
+
- clean rebuild the solution
49
+
- run tests against release
50
+
28
51
-----
29
52
### Developer checks
30
53
(Leave tasks unticked if they haven't been appropriate for your ticket.)
@@ -43,8 +66,10 @@ I have:
43
66
-[ ] Updated my Jira ticket with testing notes, including information about other parts of the system that were touched as part of the PR and need to be tested to ensure nothing is broken
44
67
-[ ] Tested in [Dev Showcase](https://technologyenhancedlearning.github.io/TELBlazor-DevShowCase/) (including logging by using log level switcher)
45
68
-[ ] Scanned over my pull request and commented with any useful explanations/questions to reviewers
46
-
-[ ] Scanned over cicd warnings
47
-
69
+
-[ ] Scanned over cicd warnings relating to the component or area of code I have worked on (give the general ones a look too but antyhing in OptionalImplementations/Test can be ignored)
70
+
-[ ] Maybe? Audit NuGet packages; use lightweight ones (e.g., System.Text.Json); ensure third-party components support trimming.
71
+
-[ ] Scanned in visual studio build info messages about improving code for new code
72
+
-[ ]
48
73
---
49
74
### Peer Reviewers and Assignee checks before Approval
#3. Install wasm-tools this allows delinking so we can have smalled wasm files producted by client projects consuming the Package. Specifying nuget to stop azure package issues.
@@ -335,6 +338,8 @@ recommend tool it is designed for though both support the others tool.
335
338
- not using guid id as i have elsewhere either [Parameter] public string ElementId { get; set; } = $"tel-button-{Guid.NewGuid():N}";
336
339
- various things have been cut from mvcblazor so it is worth returning to for potential solutions if developing this solution [MVCBlazor repo](https://github.com/TechnologyEnhancedLearning/MVCBlazor)
Copy file name to clipboardExpand all lines: TELBlazor.Components.ShowCase.E2ETests.WasmServerHost/TELBlazor.Components.ShowCase.E2ETests.WasmServerHost.Client/TELBlazor.Components.ShowCase.E2ETests.WasmServerHost.Client.csproj
0 commit comments