10739 results for "test"

  • sadly I think capjamesg fixed his bug that triggered the 500, so I don't have an easy way to test your fix
    [snarfed] at 2025-01-03 06:28
  • I really love how the IndieAuth and Micropub specs come with a test suite! (And now I see Authorship too) IndieWeb++
    carrvo[d] at 2025-01-02 21:34
  • [jeremycherfas.net] This is a bit embarassing. For I think the first time, I gave this post the same title as a previous post, which I realised only because that post had received webmentions that displayed on this place. The only solution is to retitle this post and reshare it. And ensure I test... (https://www.jeremycherfas.net/blog/listen-to-what)
    Loqi at 2025-01-02 15:05
  • capjamesg[d], one way to test the fidelity is to see if it roundtrips and produces the same PNG
    [tantek] at 2025-01-01 22:50
  • (speaking of things that need a test suite)
    aaronpk at 2024-12-31 16:09
  • [edit] Hi! I'm working on MicroPub for my private blogging system (https://havenweb.org) and trying to test it with Quill (https://quill.p3k.io). It looks like the spec (https://micropub.spec.indieweb.org/#create) calls for defining type with an 'h' parameter that has a value of 'entry', but I'm seeing Quill send a 'type' parameter with a value of 'h-entry'. Am I interpreting the spec correctly? or is there an extension tha
    havenmatt at 2024-12-30 19:27
  • Hi! I'm working on MicroPub for my private blogging system (https://havenweb.org) and trying to test it with Quill (https://quill.p3k.io). It looks like the spec (https://micropub.spec.indieweb.org/#create) calls for defining type with an 'h' parameter that has a value of 'entry', but I'm seeing Quill send a 'type' parameter with a value of 'h-entry'. Am I interpreting the spec correctly? or is there an extension that I sho
    havenmatt at 2024-12-30 19:27
  • I'm hoping to get this live in a few days for people to test and use!
    capjamesg[d] at 2024-12-28 23:29
  • GWG For testing 3rd party I know of 3 approaches that can be used in combination: 1) mock their interfaces to unit test just your code, 2) write tests against their API (helps with both learning and ability to test compatibility of new releases), and 3) write a wrapper around their API so that you have an interface that makes sense for your app (and only expose what you want).
    carrvo[d] at 2024-12-28 20:51
  • GWG your question is reminding me I have some webmention code that relies, obviously, on http://webmention.io. I might add mocking to a unit test of that class.
    [Joe_Crawford] at 2024-12-28 19:03
Sort by:
Relevance Date


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
Powered by phinde, the self-hosted search engine. status