10336
results for "test"
-
↩️ both be aware of what devices are target users are on and be mindful that the devices we test on may not always be as representative of them (but should aim to be). #webperformance https://indieweb.social/@addyosmani/109429224923281118 (2/2)
Loqi
at
2022-11-29 23:55
-
accicarello I used to have a suite of tests to validate my mf2, but my site got too big for me to test it so often so I stopped
[jamietanna]
at
2022-11-29 22:45
-
[Webmention Rocks!] Discovery Test #1
Loqi
at
2022-11-29 19:57
-
you should be able to use this to see if your webmention sending is working https://webmention.rocks/test/1 just make a post that mentions that URL
aaronpk
at
2022-11-29 19:57
-
I did but it didn’t seem to work. But maybe I just need to understand what a test case would be to test it. How would you test it?
[Michelle_Moore]
at
2022-11-29 19:53
-
it would make a good e-* parsing test case!
[tantek]
at
2022-11-29 18:37
-
hmm s/the test suite/monocle isn’t picking up you as being the reposter though https://monocle.p3k.io/preview?url=https://acegiak.net
barnaby
at
2022-11-26 14:47
-
tidying up the test suites for standards we maintain is a better use of our time IMO — e.g. adding PKCE support to the micropub test suite, making an indieauth test suite
barnaby
at
2022-11-23 17:06
-
you mean we can't just put up the old test suite and say "mastodon is wrong, fix mastodon"?? 😏
[schmarty]
at
2022-11-23 17:05
-
this is literally what happens when there's no test suite to keep a spec "anchored", and do test-drive spec iteration / development
[tantek]
at
2022-11-23 17:04
Sort by:
Filter results by:
Tag
Query took 0.01s.
Search tips
- Exclusion
- +foo -bar
- Logical OR
- foo OR bar
- Exact phrase
- "foo bar"
- Partial words
- foo*
- Particular fields only
- title:foo
- domain:example.org
- nick:somebody
- after:2016-11-23
- before:2016-11-23
- date:2016-11-23