From: Max Nikulin <manikulin@gmail.com>
To: Ilya Chernyshov <ichernyshovvv@gmail.com>,
emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] testing: Delete duplicate tests
Date: Fri, 14 Jul 2023 18:50:39 +0700 [thread overview]
Message-ID: <2e5004db-1c3c-1b5c-e665-1b538aad745c@gmail.com> (raw)
In-Reply-To: <87cz0xndem.fsf@gmail.com>
On 13/07/2023 02:22, Ilya Chernyshov wrote:
> +++ b/testing/lisp/test-ol.el
> @@ -301,14 +301,6 @@ Seehttps://github.com/yantar92/org/issues/4."
> (let ((file (buffer-file-name)))
> (equal (format "[[file:%s::two]]" file file)
> (org-store-link nil))))))
> - (should
> - (let ((org-stored-links nil)
> - (org-context-in-file-links t))
> - (org-test-with-temp-text-in-file "# two"
> - (fundamental-mode)
> - (let ((file (buffer-file-name)))
> - (equal (format "[[file:%s::two]]" file file)
> - (org-store-link nil))))))
The test was added by
7a78eb1be 2020-03-26 22:57:16 +0100 Nicolas Goaziou: ol: Fix some corner
cases when normalizing context in links
The intention may be to test "#two" besides "# two". Maybe somebody has
a better guess what case related to the change is not covered.
The idea to find duplicated tests is bright. The code may be transformed
in a dedicated unit test. I would not drop existing tests blindly though.
next prev parent reply other threads:[~2023-07-14 11:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 19:22 [PATCH] testing: Delete duplicate tests Ilya Chernyshov
2023-07-13 9:51 ` Ihor Radchenko
2023-08-08 12:44 ` Ihor Radchenko
2023-08-31 6:17 ` Ilya Chernyshov
2023-08-31 6:29 ` Ihor Radchenko
2023-11-08 9:59 ` Ihor Radchenko
2023-11-11 8:55 ` Ilya Chernyshov
2023-11-16 12:27 ` Ilya Chernyshov
2024-01-16 13:44 ` Ihor Radchenko
2024-01-23 12:03 ` Ilya Chernyshov
2024-01-26 13:24 ` Ihor Radchenko
2024-01-27 5:04 ` Ilya Chernyshov
2024-01-31 12:17 ` Ihor Radchenko
2024-02-09 12:22 ` Ilya Chernyshov
2024-02-09 14:11 ` Ihor Radchenko
2023-07-14 11:50 ` Max Nikulin [this message]
2023-07-15 7:56 ` Ihor Radchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2e5004db-1c3c-1b5c-e665-1b538aad745c@gmail.com \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=ichernyshovvv@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).