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
Copy file name to clipboardExpand all lines: _TODO.md
+26-21Lines changed: 26 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,9 +3,9 @@
3
3
4
4
## E2E Files with Skipped Tests
5
5
6
-
Blocked Categories (44 tests):
6
+
`FORCE_COLOR=1 CI=1 npx playwright test`
7
7
8
-
Visual regression testing (18)
8
+
## Visual Regression Testing
9
9
10
10
Playwright's Built-in Visual Testing
11
11
@@ -17,33 +17,23 @@ Pros: It's free, everything stays local (no third-party services needed), setup
17
17
18
18
Cons: Browser rendering can be inconsistent across different operating systems and machines, leading to "flaky" tests or false positives. Managing baselines for multiple browsers and resolutions manually can also be challenging at scale.
19
19
20
-
Axe accessibility (2) - axe-core integration
21
-
22
20
## Missing E2E Component Tests
23
21
22
+
- BugReporter
23
+
- Calendar
24
24
- Code/CodeBlock
25
25
- Code/CodeTabs
26
26
- Consent/Checkbox
27
-
28
-
## Youtube video for Backstage IDP hero on Home page
29
-
30
-
Discuss agentic AI integrations to add to Backstage
27
+
- Diagram
28
+
- FileExplorer
29
+
- Inset
30
+
- Time
31
+
- Troubleshooter
31
32
32
33
## Performance
33
34
34
35
Implement mitigations in test/e2e/specs/07-performance/PERFORMANCE.md
## Move Docker containers to dev server from Playwright
44
-
45
-
We should start the mock containers with the dev server instead of with Playwright so that they're useable in a dev environment.
46
-
47
37
## Print
48
38
49
39
- Improve print layout by hiding header and footer for articles, add tracking
@@ -109,7 +99,7 @@ Hide any interactive or screen-specific components using display: none; in your
109
99
110
100
3. Expand External Links For Print:
111
101
112
-
We can't (yet) directly interface with a printed page to explore links, so link URLs should be visible on the printed version of the Web page. To keep the page relatively clean, I prefer to expand only outbound links in articles, and suppress internal ones. If you've used relative URLs on your website for local links, you can easily do this through an attribute selector and :after pseudo=classes, thus preventing internal links and links around images from being printed:
102
+
We can't (yet) directly interface with a printed page to explore links, so link URLs should be visible on the printed version of the Web page. To keep the page relatively clean, I prefer to expand only outbound links in articles, and suppress internal ones. If you've used relative URLs on your website for local links, you can easily do this through an attribute selector and `:after` pseudoclasses, thus preventing internal links and links around images from being printed:
113
103
114
104
```css
115
105
@mediaprint {
@@ -188,7 +178,22 @@ The text, diagrams, and images in this work are licensed under CC BY-NC 4.0
188
178
All code samples in this article are licensed under the MIT License. Feel free to use, modify, and distribute them in any project.
189
179
```
190
180
191
-
## Todo
181
+
## Youtube video for Backstage IDP hero on Home page
182
+
183
+
Discuss agentic AI integrations to add to Backstage
0 commit comments