#REDIRECT [[Regression Testing]]
...
32 bytes (3 words) - 02:53, 20 January 2016
#REDIRECT [[Regression Testing#Patching your git tree]]
...
55 bytes (7 words) - 05:39, 16 November 2016
These instructions will allow you to run a regression test between recent versions of Wine and very old ones (which often have tr
...gression is to do [[Regression Testing|regression testing]]. But the usual regression testing procedure will fail to work in some cases: you cannot compile (or r
...
10 KB (1,595 words) - 21:11, 12 March 2016
If you find any regressions, please run a [[Regression Testing|regression test]] and [[Bugs|file a bug]].
...
3 KB (494 words) - 22:58, 22 April 2018
...found in the Wine source code because the author of a patch that causes a regression is unaware of it. Since the Wine developers can't possibly test every appli
If your application has experienced a regression, please try and provide us with as much information as you can about when a
...
7 KB (1,246 words) - 18:45, 10 February 2018
* [[Regression Testing|回归测试]]指南。
...
4 KB (198 words) - 15:15, 4 March 2021
==How to do regression testing using Git ==
...tween wine-1.1.42 and wine-1.1.44 (these are [WWW] release tags). To start regression testing we run:</p>
...
10 KB (1,717 words) - 05:06, 8 November 2023
...ches may be committed before someone notices the regression. This is where regression testing comes in.
...t and Wine together, see [[Git Wine Tutorial]]; this article is focused on regression testing.
...
21 KB (3,370 words) - 21:23, 4 August 2023
...if you have access to the program and can confirm the bug, you can try the regression test yourself if you wish). If the test succeeds, have the reporter note th
...ll this in. The most commonly used are '''download''', '''installer''', '''regression''', and '''source'''.
...
15 KB (2,516 words) - 23:19, 29 February 2016
**2005_05_01_15_07_37.avi Paul & Jeremy W. - CxTest: automatic full-GUI regression tests
* A How-to For Regression Testing [Gouget]
...
7 KB (995 words) - 17:12, 8 May 2018
* Is it a regression? See [[Regression Testing]]
...
7 KB (1,202 words) - 02:08, 1 March 2016
* Instructions for [[Regression Testing]].
...
4 KB (552 words) - 11:36, 5 March 2021
...d as normal; you can find some (admittedly rather outdated) instructions [[Regression Testing|here]].
...a problem introduced or exposed by a patch committed upstream, that is, a regression strictly in upstream Wine. Again, we really need to know which one of these
...
15 KB (2,608 words) - 04:58, 3 November 2023
* [[Regression Testing|회기 시험]] 명령
...
4 KB (99 words) - 13:08, 11 October 2019
...on the working/broken versions. If you can, running a [[Regression_Testing|regression test]] is very helpful.
...
9 KB (1,590 words) - 07:05, 16 February 2024
* The Wiki page on [[Regression Testing]] (which is aimed at non-programmers).
=== Regression testing ===
...
25 KB (4,190 words) - 21:02, 16 December 2022
* [[Regression Testing|Achteruitgang in de ontwikkeling]] van Wine opsporen.
...
4 KB (618 words) - 22:55, 8 September 2022
* Instruktionen hinsichtlich [[Regression Testing]].
...
4 KB (549 words) - 15:13, 4 March 2021
* Instructions pour les [[Regression Testing|tests de régression]].
...
4 KB (621 words) - 15:11, 4 March 2021
* runtest - wrapper script to run one of the Wine regression tests from inside the build tree
...
5 KB (752 words) - 11:22, 12 April 2016
====Run a git bisect on a regression on the lower part of https://source.winehq.org/regressions====
...
7 KB (1,244 words) - 00:06, 26 April 2018
If you're interested in [[Submitting Patches]] or [[Regression Testing]] though, you'll want to build Wine from the tip of WineHQ's [[Git
...
9 KB (1,431 words) - 03:08, 4 May 2023
Building from git is necessary to run regression tests or test patches.
...
10 KB (1,570 words) - 14:37, 21 July 2018
...ules make the merge request easier to review, and also make it easier to [[Regression Testing|find regressions]], and help prevent new bugs from slipping through
...
15 KB (2,621 words) - 13:58, 24 September 2023
For optimizing specific codepaths or having very sensitive regression detection microbenchmarks are an option. They test a very narrow aspect of
...
18 KB (2,961 words) - 17:47, 21 September 2022
...then there is no need to keep submitting test results. If you have found a regression in a newer version then you should open a bug report to get it fixed. If th
...
17 KB (2,781 words) - 19:07, 16 July 2019
...are being run. This would make it hard to detect new failures caused by a regression. or to detect that a patch fixed a long standing issue.
...
21 KB (3,595 words) - 17:02, 13 November 2019
...the Wine-Devel mailing lists, watches daily valgrind runs and does regular regression-testing is the overall expert and awesome dude: Dan Kegel."
...age the Computer-Cluster that build the winetest binaries and run the Wine Regression Tests [http://source.winehq.org/git/wine.git/?a=search&h=HEAD&st=author&s=P
...
39 KB (6,163 words) - 15:03, 23 October 2019
...ch caused it, then [http://bugs.winehq.org file a bug report] and add the "regression" keyword: we'll pay special attention to it, since regressions are a lot ea
...
75 KB (12,532 words) - 20:00, 15 March 2024
* devel/ccache (for [[Regression Testing]])
...
22 KB (3,621 words) - 21:41, 4 August 2023
...ch caused it, then [http://bugs.winehq.org file a bug report] and add the "regression" keyword: we'll pay special attention to it, since regressions are a lot ea
...
74 KB (11,516 words) - 20:56, 4 August 2023
...ring de fout heeft veroorzaakt]]. Maak daarna een foutrapport en gebruik ''regression'' als sleutelwoord. Deze rapportages krijgen extra aandacht van de ontwikke
...
61 KB (9,374 words) - 17:16, 22 January 2024
...anciennes ne tournent plus dans la nouvelle version (cela s'appelle des [[Regression|régressions]]), ainsi que des problèmes causés par l'introduction de nouvel
...;développement » : des versions ultérieures peuvent causer des [[regression|régressions]].
...
97 KB (15,559 words) - 21:26, 4 August 2023
