{"title":"Triagem de tickets","version":"5.2","locale":"pt-br","docname":"internals/contributing/triaging-tickets","url":"/pt-br/5.2/internals/contributing/triaging-tickets/","canonical":"https://djangodocs.dev/pt-br/5.2/internals/contributing/triaging-tickets/","summary":"Django uses Trac for managing the work on the code base. Trac is a community-tended garden of the bugs people have found and the features Django has decided to add.…","html":"<h1>Triagem de tickets<a class=\"heading-anchor\" href=\"#triaging-tickets\"><span class=\"visually-hidden\">Link para este cabeçalho</span><span aria-hidden=\"true\">#</span></a></h1>\n<p>Django uses <a class=\"reference external\" href=\"https://code.djangoproject.com/\">Trac</a> for managing the work on the code base. Trac is a\ncommunity-tended garden of the bugs people have found and the features Django\nhas decided to add. As in any garden, sometimes there are weeds to be pulled\nand sometimes there are flowers and vegetables that need picking. We need your\nhelp to sort out one from the other, and in the end, we all benefit together.</p>\n<p>Like all gardens, we can aspire to perfection, but in reality there’s no such\nthing. Even in the most pristine garden there are still snails and insects.\nIn a community garden there are also helpful people who – with the best of\nintentions – fertilize the weeds and poison the roses. It’s the job of the\ncommunity as a whole to self-manage, keep the problems to a minimum, and\neducate those coming into the community so that they can become valuable\ncontributing members.</p>\n<p>Similarly, while we aim for Trac to be a perfect representation of the state of\nDjango’s progress, we acknowledge that this will not happen. By distributing\nthe load of Trac maintenance to the community, we accept that there will be\nmistakes. Trac is “mostly accurate”, and we give allowances for the fact that\nsometimes it will be wrong. That’s okay. We’re perfectionists with deadlines.</p>\n<p>We rely on the community to keep participating, keep tickets as accurate as\npossible, and raise issues for discussion on the <a class=\"reference external\" href=\"https://forum.djangoproject.com/\">Django Forum</a> when there is\nconfusion or disagreement.</p>\n<p>Django é um projeto comunitário, e cada contribuição ajuda. Nós não podemos fazer isso sem <strong>vocês</strong>!</p>\n<section id=\"triage-workflow\">\n<h2>Fluxo de triagem<a class=\"heading-anchor\" href=\"#triage-workflow\"><span class=\"visually-hidden\">Link para este cabeçalho</span><span aria-hidden=\"true\">#</span></a></h2>\n<p>Unfortunately, not all reports in the ticket tracker provide all the\n<a class=\"reference internal\" href=\"/pt-br/5.2/internals/contributing/bugs-and-features/\"><span class=\"doc\">required details</span></a>. A number of tickets have proposed\nsolutions, but those don’t necessarily meet all the requirements <a class=\"reference internal\" href=\"/pt-br/5.2/internals/contributing/writing-code/submitting-patches/#patch-style\"><span class=\"std std-ref\">adhering\nto the guidelines for contributing</span></a>.</p>\n<p>One way to help out is to <em>triage</em> tickets that have been created by other\nusers.</p>\n<p>A maior parte do fluxo de trabalho é baseada em torno do conceito de tickets <a class=\"reference internal\" href=\"#triage-stages\"><span class=\"std std-ref\">estágios de triagem</span></a>. Cada estágio descreve em que parte de seu clico de vida um ticket está em um dado momento. Além de várias tags, esse atributo nos diz claramente o que e quem o ticket está aguardando.</p>\n<p>Já que uma imagem vale mais que mil palavras, vamos começar aqui:</p>\n<a class=\"reference internal image-reference\" href=\"../../../../../../_images/triage_process.svg\"><img alt=\"Django's ticket triage workflow\" src=\"/pt-br/5.2/_images/triage_process.svg\" style=\"width: 600px; height: 750px;\" />\n</a>\n<p>Nós temos dois papéis neste diagrama:</p>\n<ul class=\"simple\">\n<li><p>Mergers: people with commit access who are responsible for making the\nfinal decision to merge a change.</p></li>\n<li><p>Agentes de triagem: qualquer pessoa na comunidade Django que escolher se envolver no processo de desenvolvimento do Django. Nossa instalação do Trac é intencionalmente deixada aberta para o público, e qualquer pessoa pode fazer a triagem dos tickets. Django é um projeto comunitário, e nós encorajamos <a class=\"reference internal\" href=\"#how-can-i-help-with-triaging\"><span class=\"std std-ref\">triagens feitas pela comunidade</span></a>.</p></li>\n</ul>\n<p>Como exemplo, aqui nós podemos ver o ciclo de vida de um ticket comum:</p>\n<ul class=\"simple\">\n<li><p>Alice creates a ticket and sends an incomplete pull request (no tests,\nincorrect implementation).</p></li>\n<li><p>Bob reviews the pull request, marks the ticket as “Accepted”, “needs tests”,\nand “patch needs improvement”, and leaves a comment telling Alice how the\npatch could be improved.</p></li>\n<li><p>Alice updates the pull request, adding tests (but not changing the\nimplementation). She removes the two flags.</p></li>\n<li><p>Charlie reviews the pull request and resets the “patch needs improvement”\nflag with another comment about improving the implementation.</p></li>\n<li><p>Alice updates the pull request, fixing the implementation. She removes the\n“patch needs improvement” flag.</p></li>\n<li><p>Daisy reviews the pull request and marks the ticket as “Ready for checkin”.</p></li>\n<li><p>Jacob, a <a class=\"reference internal\" href=\"/pt-br/5.2/internals/organization/#mergers-team\"><span class=\"std std-ref\">merger</span></a>, reviews the pull request and merges\nit.</p></li>\n</ul>\n<p>Alguns tickets precisam de bem menos feedback do que esse, mas então novamente outros tickets requerem muito, muito mais.</p>\n</section>\n<section id=\"triage-stages\">\n<span id=\"id1\"></span><h2>Estágios de triagem<a class=\"heading-anchor\" href=\"#triage-stages\"><span class=\"visually-hidden\">Link para este cabeçalho</span><span aria-hidden=\"true\">#</span></a></h2>\n<p>Abaixo são descritos em mais detalhes os vários estágios que um ticket pode possuir durante o seu tempo de vida.</p>\n<section id=\"unreviewed\">\n<h3>Não revisado<a class=\"heading-anchor\" href=\"#unreviewed\"><span class=\"visually-hidden\">Link para este cabeçalho</span><span aria-hidden=\"true\">#</span></a></h3>\n<p>The ticket has not been reviewed by anyone who felt qualified to make a\njudgment about whether the ticket contained a valid issue or ought to be closed\nfor any of the various reasons.</p>\n</section>\n<section id=\"accepted\">\n<h3>Aceito<a class=\"heading-anchor\" href=\"#accepted\"><span class=\"visually-hidden\">Link para este cabeçalho</span><span aria-hidden=\"true\">#</span></a></h3>\n<p>A grande área cinzenta! O sentido absoluto de “aceito” é que o problema descrito no ticket é válido e está em algum estágio no processo de ser resolvido. Além disso existem vários considerações:</p>\n<ul>\n<li><p><strong>Aceito + Nenhuma Tag</strong></p>\n<p>The ticket is valid, but no one has submitted a patch for it yet. Often this\nmeans you could safely start writing a fix for it. This is generally more\ntrue for the case of accepted bugs than accepted features. A ticket for a bug\nthat has been accepted means that the issue has been verified by at least one\ntriager as a legitimate bug - and should probably be fixed if possible.</p>\n<p>For new features, accepted tickets should only exist after the idea has gone\nthrough the appropriate <a class=\"reference internal\" href=\"/pt-br/5.2/internals/contributing/bugs-and-features/#requesting-features\"><span class=\"std std-ref\">process for suggesting new features</span></a> and received community and <a class=\"reference internal\" href=\"/pt-br/5.2/internals/organization/#steering-council\"><span class=\"std std-ref\">Steering Council</span></a> approval, or been accepted in a DEP.</p>\n</li>\n<li><p><strong>Aceito + Possui Patch</strong></p>\n<p>The ticket is waiting for people to review the supplied solution. This means\ndownloading the patch and trying it out, verifying that it contains tests\nand docs, running the test suite with the included patch, and leaving\nfeedback on the ticket.</p>\n</li>\n<li><p><strong>Aceito + Possui Patch + Precisa …</strong></p>\n<p>Isso significa que o ticket foi revisado, e constatado que ele precisa de mais trabalho. “Precisa de testes” e “Precisa de documentação” são auto-explicativos. “Patch precisa de melhorias” geralmente estará acompanhado de um comentário no ticket explicando o que ele precisa para melhorar.</p>\n</li>\n</ul>\n</section>\n<section id=\"ready-for-checkin\">\n<h3>Pronto para Checkin<a class=\"heading-anchor\" href=\"#ready-for-checkin\"><span class=\"visually-hidden\">Link para este cabeçalho</span><span aria-hidden=\"true\">#</span></a></h3>\n<p>The ticket was reviewed by any member of the community other than the person\nwho supplied the patch and found to meet all the requirements for a\ncommit-ready contribution. A <a class=\"reference internal\" href=\"/pt-br/5.2/internals/organization/#mergers-team\"><span class=\"std std-ref\">merger</span></a> now needs to give\na final review prior to being committed.</p>\n<p>There are a lot of pull requests. It can take a while for your patch to get\nreviewed. See the <a class=\"reference internal\" href=\"/pt-br/5.2/faq/contributing/#new-contributors-faq\"><span class=\"std std-ref\">contributing code FAQ</span></a> for some\nideas here.</p>\n</section>\n<section id=\"someday-maybe\">\n<h3>Algum Dia/Talvez<a class=\"heading-anchor\" href=\"#someday-maybe\"><span class=\"visually-hidden\">Link para este cabeçalho</span><span aria-hidden=\"true\">#</span></a></h3>\n<p>This stage isn’t shown on the diagram. It’s used sparingly to keep track of\nlong-term changes.</p>\n<p>These tickets are uncommon and overall less useful since they don’t describe\nconcrete actionable issues.</p>\n</section>\n</section>\n<section id=\"other-triage-attributes\">\n<h2>Outros atributos de triagem<a class=\"heading-anchor\" href=\"#other-triage-attributes\"><span class=\"visually-hidden\">Link para este cabeçalho</span><span aria-hidden=\"true\">#</span></a></h2>\n<p>Um número de tags, aparecendo como checkboxes no Trac, podem ser ativdadas no ticket:</p>\n<section id=\"has-patch\">\n<h3>Possui patch<a class=\"heading-anchor\" href=\"#has-patch\"><span class=\"visually-hidden\">Link para este cabeçalho</span><span aria-hidden=\"true\">#</span></a></h3>\n<p>This means the ticket has an associated solution. These will be reviewed to\nensure they adhere to the <a class=\"reference internal\" href=\"/pt-br/5.2/internals/contributing/writing-code/submitting-patches/\"><span class=\"doc\">documented guidelines</span></a>.</p>\n<p>Os três campos seguintes (Precisa de documentação, Precisa de testes, Patch precisa de melhorias) se aplicam apenas se o patch foi submetido.</p>\n</section>\n<section id=\"needs-documentation\">\n<h3>Precisa de documentação<a class=\"heading-anchor\" href=\"#needs-documentation\"><span class=\"visually-hidden\">Link para este cabeçalho</span><span aria-hidden=\"true\">#</span></a></h3>\n<p>Essa tag é usada para tickets com patches sem documentação associada.  Documentação completa de funcionalidades é um pré-requisito antes de nós adicionarmos elas no código base.</p>\n</section>\n<section id=\"needs-tests\">\n<h3>Precisa de testes<a class=\"heading-anchor\" href=\"#needs-tests\"><span class=\"visually-hidden\">Link para este cabeçalho</span><span aria-hidden=\"true\">#</span></a></h3>\n<p>This flags the patch as needing associated unit tests. Again, this\nis a required part of a valid contribution.</p>\n</section>\n<section id=\"patch-needs-improvement\">\n<h3>Patch precisa de melhorias<a class=\"heading-anchor\" href=\"#patch-needs-improvement\"><span class=\"visually-hidden\">Link para este cabeçalho</span><span aria-hidden=\"true\">#</span></a></h3>\n<p>This flag means that although the ticket <em>has</em> a solution, it’s not quite\nready for checkin. This could mean the patch no longer applies\ncleanly, there is a flaw in the implementation, or that the code\ndoesn’t meet our standards.</p>\n</section>\n<section id=\"easy-pickings\">\n<h3>Escolhas Fáceis<a class=\"heading-anchor\" href=\"#easy-pickings\"><span class=\"visually-hidden\">Link para este cabeçalho</span><span aria-hidden=\"true\">#</span></a></h3>\n<p>Tickets that would require small, easy, changes.</p>\n</section>\n<section id=\"type\">\n<h3>Tipo<a class=\"heading-anchor\" href=\"#type\"><span class=\"visually-hidden\">Link para este cabeçalho</span><span aria-hidden=\"true\">#</span></a></h3>\n<p>Os tickets devem ser categorizados por <em>tipo</em> entre:</p>\n<ul class=\"simple\">\n<li><dl class=\"simple\">\n<dt>Nova funcionalidade</dt><dd><p>Para adicionar algo novo.</p>\n</dd>\n</dl>\n</li>\n<li><dl class=\"simple\">\n<dt>Bug</dt><dd><p>Para quando algo que já existe está quebrado ou não se comporta como esperado.</p>\n</dd>\n</dl>\n</li>\n<li><dl class=\"simple\">\n<dt>Limpeza/otimização</dt><dd><p>Para quando nada está quebrado mas algo poderia ser mais limpo, melhor, rápido, forte.</p>\n</dd>\n</dl>\n</li>\n</ul>\n</section>\n<section id=\"component\">\n<h3>Componente<a class=\"heading-anchor\" href=\"#component\"><span class=\"visually-hidden\">Link para este cabeçalho</span><span aria-hidden=\"true\">#</span></a></h3>\n<p>Tickets devem ser classificados dentro de <em>componentes</em> indicando qual área do código base do Django eles pertencem. Isso faz com que os tickets fiquem melhor organizados e mais fáceis de encontrar.</p>\n</section>\n<section id=\"severity\">\n<h3>Severidade<a class=\"heading-anchor\" href=\"#severity\"><span class=\"visually-hidden\">Link para este cabeçalho</span><span aria-hidden=\"true\">#</span></a></h3>\n<p>The <em>severity</em> attribute is used to identify blockers, that is, issues that\nshould get fixed before releasing the next version of Django. Typically those\nissues are bugs causing regressions from earlier versions or potentially\ncausing severe data losses. This attribute is quite rarely used and the vast\nmajority of tickets have a severity of “Normal”.</p>\n</section>\n<section id=\"version\">\n<h3>Versão<a class=\"heading-anchor\" href=\"#version\"><span class=\"visually-hidden\">Link para este cabeçalho</span><span aria-hidden=\"true\">#</span></a></h3>\n<p>É possível usar o atributo “versão” para indicar em qual versão o bug relatado foi identificado.</p>\n</section>\n<section id=\"ui-ux\">\n<h3>UI/UX<a class=\"heading-anchor\" href=\"#ui-ux\"><span class=\"visually-hidden\">Link para este cabeçalho</span><span aria-hidden=\"true\">#</span></a></h3>\n<p>Esta tag é utilizada para tickets que estão relacionados a questões de interface de usuário e de experiência de usuário. Por exemplo, essa tag seria apropriada para funcionalidades que os usuários podem ver nos formulários ou na interface do admin.</p>\n</section>\n<section id=\"cc\">\n<h3>Cc<a class=\"heading-anchor\" href=\"#cc\"><span class=\"visually-hidden\">Link para este cabeçalho</span><span aria-hidden=\"true\">#</span></a></h3>\n<p>Você pode adicionar o seu nome de usuário ou endereço de email neste campo para ser notificado quando novas contribuições forem feitas ao ticket.</p>\n</section>\n<section id=\"keywords\">\n<h3>Palavras-chave<a class=\"heading-anchor\" href=\"#keywords\"><span class=\"visually-hidden\">Link para este cabeçalho</span><span aria-hidden=\"true\">#</span></a></h3>\n<p>With this field you may label a ticket with multiple keywords. This can be\nuseful, for example, to group several tickets on the same theme. Keywords can\neither be comma or space separated. Keyword search finds the keyword string\nanywhere in the keywords. For example, clicking on a ticket with the keyword\n“form” will yield similar tickets tagged with keywords containing strings such\nas “formset”, “modelformset”, and “ManagementForm”.</p>\n</section>\n</section>\n<section id=\"closing-tickets\">\n<span id=\"id2\"></span><h2>Fechando Tickets<a class=\"heading-anchor\" href=\"#closing-tickets\"><span class=\"visually-hidden\">Link para este cabeçalho</span><span aria-hidden=\"true\">#</span></a></h2>\n<p>When a ticket has completed its useful lifecycle, it’s time for it to be\nclosed. Closing a ticket is a big responsibility, though. You have to be sure\nthat the issue is really resolved, and you need to keep in mind that the\nreporter of the ticket may not be happy to have their ticket closed (unless\nit’s fixed!). If you’re not certain about closing a ticket, leave a comment\nwith your thoughts instead.</p>\n<p>Se você realmente for fechar um ticket, você sempre deve ter certeza de que:</p>\n<ul class=\"simple\">\n<li><p>Certifique-se de que o problema foi resolvido.</p></li>\n<li><p>Deixe um comentário explicando a decisão de fechar o ticket.</p></li>\n<li><p>Se existe uma forma de melhorar o ticket para que ele seja reaberto, informe como.</p></li>\n<li><p>Se o ticket está duplicado, faz uma referência ao ticket original. Também faça uma referência cruzada no ticket fechado deixando um comentário no ticket original – isso permite acessar mais informações sobre o bug relatado ou a funcionalidade solicitada.</p></li>\n<li><p><strong>Seja educado</strong> Ninguém gosta de ter o seu ticket fechado. Isso pode ser frustrante e até mesmo desencorajante. A melhor forma de evitar que pessoas deixem de contribuir com o Django é sendo gentil e educado oferecendo sugestões sobre como eles podem melhorar esse ticket e outros tickets no futuro.</p></li>\n</ul>\n<p>Um ticket pode ser resolvido de diversas maneiras:</p>\n<ul class=\"simple\">\n<li><dl class=\"simple\">\n<dt>Corrigido</dt><dd><p>Used once a patch has been rolled into Django and the issue is fixed.</p>\n</dd>\n</dl>\n</li>\n<li><dl class=\"simple\">\n<dt>Inválido</dt><dd><p>Utilizado caso constatado que o ticket estava incorreto. Isso significa que o problema relatado no ticket é na verdade o resultado de um erro cometido pelo usuário, ou descreve um problema com algo não relacionado ao Django, ou se não é um relato de um bug ou a solicitação de uma nova funcionalidade (por exemplo, alguns novos usuários enviam dúvidas de suporte como tickets).</p>\n</dd>\n</dl>\n</li>\n<li><dl class=\"simple\">\n<dt>wontfix</dt><dd><p>Used when someone decides that the request isn’t appropriate for\nconsideration in Django. Sometimes a ticket is closed as “wontfix” with a\nrequest for the reporter to start a discussion on the <a class=\"reference external\" href=\"https://forum.djangoproject.com/\">Django Forum</a> if\nthey feel differently from the rationale provided by the person who\nclosed the ticket. Other times, a discussion precedes the decision to\nclose a ticket. Always use the forum to get a consensus before reopening\ntickets closed as “wontfix”.</p>\n</dd>\n</dl>\n</li>\n<li><dl class=\"simple\">\n<dt>Duplicado</dt><dd><p>Usado quando outro ticket cobre o mesmo problema. Fechando tickets duplicados, nós mantemos toda a discussão em um só local, o que ajuda todo mundo.</p>\n</dd>\n</dl>\n</li>\n<li><dl class=\"simple\">\n<dt>worksforme</dt><dd><p>Usado quando o ticket não contém detalhes o suficiente para replicar o bug original.</p>\n</dd>\n</dl>\n</li>\n<li><dl class=\"simple\">\n<dt>needsinfo</dt><dd><p>Usado quando o ticket não contém informação o suficiente para replicar o problema relatado mas ainda tem o potencial de ser válido. O ticket deve ser reaberto quando mais informações foram fornecidas.</p>\n</dd>\n</dl>\n</li>\n</ul>\n<p>If you believe that the ticket was closed in error – because you’re\nstill having the issue, or it’s popped up somewhere else, or the triagers have\nmade a mistake – please reopen the ticket and provide further information.\nAgain, please do not reopen tickets that have been marked as “wontfix” and\nbring the issue to the <a class=\"reference external\" href=\"https://forum.djangoproject.com/\">Django Forum</a> instead.</p>\n</section>\n<section id=\"how-can-i-help-with-triaging\">\n<span id=\"id3\"></span><h2>Como eu posso ajudar com a triagem?<a class=\"heading-anchor\" href=\"#how-can-i-help-with-triaging\"><span class=\"visually-hidden\">Link para este cabeçalho</span><span aria-hidden=\"true\">#</span></a></h2>\n<p>O processo de triagem é controlado primeiramente pelos membros da comunidade. De verdade, <strong>QUALQUER PESSOA</strong> pode ajudar.</p>\n<p>Para contribuir, comece <a class=\"reference external\" href=\"https://www.djangoproject.com/accounts/password/reset/\">criando uma conta no Trac</a>. Se você tem uma conta mas esqueceu a sua senha, você pode resetá-la usando a <a class=\"reference external\" href=\"https://www.djangoproject.com/accounts/register/\">página de recuperação de senha</a>.</p>\n<p>A partir disso, você poderá ajudar com:</p>\n<ul class=\"simple\">\n<li><p>Closing “Unreviewed” tickets as “invalid”, “worksforme”, or “duplicate”, or\n“wontfix”.</p></li>\n<li><p>Closing “Unreviewed” tickets as “needsinfo” when the description is too\nsparse to be actionable.</p></li>\n<li><p>Corrigindo as flags “Needs tests”, “Needs documentation”, ou “Has patch” para tickets onde eles são setados incorretamente.</p></li>\n<li><p>Adicionando a flag “<a class=\"reference external\" href=\"https://code.djangoproject.com/query?status=!closed&amp;easy=1\">Easy pickings</a>” para tickets que são pequenos e relativamente simples.</p></li>\n<li><p>Adicionando um <em>tipo</em> para os tickets que ainda não foram categorizados.</p></li>\n<li><p>Verificando se tickets antigos ainda são válidos. Se o ticket não possui atividade em um longo período, é possível que o problema tenha sido corrigido mas o ticket ainda não foi fechado.</p></li>\n<li><p>Identifying trends and themes in the tickets. If there are a lot of bug\nreports about a particular part of Django, it may indicate we should\nconsider refactoring that part of the code. If a trend is emerging,\nyou should raise it for discussion (referencing the relevant tickets)\non the <a class=\"reference external\" href=\"https://forum.djangoproject.com/\">Django Forum</a>.</p></li>\n<li><p>Verify if solutions submitted by others are correct. If they are correct\nand also contain appropriate documentation and tests then move them to the\n“Ready for Checkin” stage. If they are not correct then leave a comment to\nexplain why and set the corresponding flags (“Patch needs improvement”,\n“Needs tests” etc.).</p></li>\n</ul>\n<aside class=\"admonition admonition-note\" role=\"note\">\n<p class=\"admonition-title\">Nota</p>\n<p>The <a class=\"reference external\" href=\"https://code.djangoproject.com/wiki/Reports\">Reports page</a> contains links to many useful Trac queries, including\nseveral that are useful for triaging tickets and reviewing proposals as\nsuggested above.</p>\n<p>Você também pode encontrar mais em <span class=\"xref std std-doc\">novos-voluntários</span>.</p>\n</aside>\n<p>Porém, nós pedimos o seguinte de todos os membros da comunidade trabalhando no banco de dados de tickets:</p>\n<ul class=\"simple\">\n<li><p>Please <strong>don’t</strong> promote your own tickets to “Ready for checkin”. You\nmay mark other people’s tickets that you’ve reviewed as “Ready for\ncheckin”, but you should get at minimum one other community member to\nreview a patch that you submit.</p></li>\n<li><p>Please <strong>don’t</strong> reverse a decision without posting a message to the\n<a class=\"reference external\" href=\"https://forum.djangoproject.com/\">Django Forum</a> to find consensus.</p></li>\n<li><p>If you’re unsure if you should be making a change, don’t make the\nchange but instead leave a comment with your concerns on the ticket,\nor post a message to the <a class=\"reference external\" href=\"https://forum.djangoproject.com/\">Django Forum</a>. It’s okay to be unsure, but your\ninput is still valuable.</p></li>\n</ul>\n</section>\n<section id=\"bisecting-a-regression\">\n<h2>Bisseccionando uma regressão<a class=\"heading-anchor\" href=\"#bisecting-a-regression\"><span class=\"visually-hidden\">Link para este cabeçalho</span><span aria-hidden=\"true\">#</span></a></h2>\n<p>Uma regressão é um bug que está presente em alguma versão nova do Django mas não em versões mais antigas. Uma informação extremamente valiosa é o commit que introduziu a regressão. Saber qual foi o commit que causou a mudança de comportamento ajuda a identificar se a mudança foi intencional ou se ela foi um efeito colateral inesperado. Aqui vamos mostrar como você pode determinar isso.</p>\n<p>Begin by writing a regression test for Django’s test suite for the issue. For\nexample, we’ll pretend we’re debugging a regression in migrations. After you’ve\nwritten the test and confirmed that it fails on the latest main branch, put it\nin a separate file that you can run standalone. For our example, we’ll pretend\nwe created <code class=\"docutils literal notranslate\"><span class=\"pre\">tests/migrations/test_regression.py</span></code>, which can be run with:</p>\n<div class=\"code-block\" data-language=\"shell\"><div class=\"code-block-toolbar\"><span class=\"code-block-language\">Shell</span><button type=\"button\" class=\"copy-button\" data-copy hidden><span class=\"copy-button-label\">Copy</span></button></div><pre role=\"group\" tabindex=\"0\" aria-label=\"Shell code\"><code>$<span class=\"w\"> </span>./runtests.py<span class=\"w\"> </span>migrations.test_regression\n</code></pre></div>\n<p>Next, we mark the current point in history as being “bad” since the test fails:</p>\n<div class=\"code-block\" data-language=\"shell\"><div class=\"code-block-toolbar\"><span class=\"code-block-language\">Shell</span><button type=\"button\" class=\"copy-button\" data-copy hidden><span class=\"copy-button-label\">Copy</span></button></div><pre role=\"group\" tabindex=\"0\" aria-label=\"Shell code\"><code>$<span class=\"w\"> </span>git<span class=\"w\"> </span>bisect<span class=\"w\"> </span>bad\nYou<span class=\"w\"> </span>need<span class=\"w\"> </span>to<span class=\"w\"> </span>start<span class=\"w\"> </span>by<span class=\"w\"> </span><span class=\"s2\">&quot;git bisect start&quot;</span>\nDo<span class=\"w\"> </span>you<span class=\"w\"> </span>want<span class=\"w\"> </span>me<span class=\"w\"> </span>to<span class=\"w\"> </span><span class=\"k\">do</span><span class=\"w\"> </span>it<span class=\"w\"> </span><span class=\"k\">for</span><span class=\"w\"> </span>you<span class=\"w\"> </span><span class=\"o\">[</span>Y/n<span class=\"o\">]</span>?<span class=\"w\"> </span>y\n</code></pre></div>\n<p>Now, we need to find a point in git history before the regression was\nintroduced (i.e. a point where the test passes). Use something like\n<code class=\"docutils literal notranslate\"><span class=\"pre\">git</span> <span class=\"pre\">checkout</span> <span class=\"pre\">HEAD~100</span></code> to check out an earlier revision (100 commits earlier,\nin this case). Check if the test fails. If so, mark that point as “bad”\n(<code class=\"docutils literal notranslate\"><span class=\"pre\">git</span> <span class=\"pre\">bisect</span> <span class=\"pre\">bad</span></code>), then check out an earlier revision and recheck. Once you\nfind a revision where your test passes, mark it as “good”:</p>\n<div class=\"code-block\" data-language=\"shell\"><div class=\"code-block-toolbar\"><span class=\"code-block-language\">Shell</span><button type=\"button\" class=\"copy-button\" data-copy hidden><span class=\"copy-button-label\">Copy</span></button></div><pre role=\"group\" tabindex=\"0\" aria-label=\"Shell code\"><code>$<span class=\"w\"> </span>git<span class=\"w\"> </span>bisect<span class=\"w\"> </span>good\nBisecting:<span class=\"w\"> </span>X<span class=\"w\"> </span>revisions<span class=\"w\"> </span>left<span class=\"w\"> </span>to<span class=\"w\"> </span><span class=\"nb\">test</span><span class=\"w\"> </span>after<span class=\"w\"> </span>this<span class=\"w\"> </span><span class=\"o\">(</span>roughly<span class=\"w\"> </span>Y<span class=\"w\"> </span>steps<span class=\"o\">)</span>\n...\n</code></pre></div>\n<p>Now we’re ready for the fun part: using <code class=\"docutils literal notranslate\"><span class=\"pre\">git</span> <span class=\"pre\">bisect</span> <span class=\"pre\">run</span></code> to automate the rest\nof the process:</p>\n<div class=\"code-block\" data-language=\"shell\"><div class=\"code-block-toolbar\"><span class=\"code-block-language\">Shell</span><button type=\"button\" class=\"copy-button\" data-copy hidden><span class=\"copy-button-label\">Copy</span></button></div><pre role=\"group\" tabindex=\"0\" aria-label=\"Shell code\"><code>$<span class=\"w\"> </span>git<span class=\"w\"> </span>bisect<span class=\"w\"> </span>run<span class=\"w\"> </span>tests/runtests.py<span class=\"w\"> </span>migrations.test_regression\n</code></pre></div>\n<p>Você deverá ver o <code class=\"docutils literal notranslate\"><span class=\"pre\">git</span> <span class=\"pre\">bisect</span></code> usando uma busca binária para automaticamente fazer checkout de revisões entre os commits bons e os commits ruins até que ele encontre o primeiro commit “ruim” onde o teste falha.</p>\n<p>Agora, mostre os seus resultados no ticket do Trac, e por favor inclua o teste de regressão como um anexo. Quando alguém escreve uma correção para o bug, eles já terão o seu teste como uma referência de por onde começar.</p>\n</section>","rootId":"triaging-tickets","toc":[{"title":"Fluxo de triagem","anchor":"triage-workflow","children":[]},{"title":"Estágios de triagem","anchor":"triage-stages","children":[{"title":"Não revisado","anchor":"unreviewed","children":[]},{"title":"Aceito","anchor":"accepted","children":[]},{"title":"Pronto para Checkin","anchor":"ready-for-checkin","children":[]},{"title":"Algum Dia/Talvez","anchor":"someday-maybe","children":[]}]},{"title":"Outros atributos de triagem","anchor":"other-triage-attributes","children":[{"title":"Possui patch","anchor":"has-patch","children":[]},{"title":"Precisa de documentação","anchor":"needs-documentation","children":[]},{"title":"Precisa de testes","anchor":"needs-tests","children":[]},{"title":"Patch precisa de melhorias","anchor":"patch-needs-improvement","children":[]},{"title":"Escolhas Fáceis","anchor":"easy-pickings","children":[]},{"title":"Tipo","anchor":"type","children":[]},{"title":"Componente","anchor":"component","children":[]},{"title":"Severidade","anchor":"severity","children":[]},{"title":"Versão","anchor":"version","children":[]},{"title":"UI/UX","anchor":"ui-ux","children":[]},{"title":"Cc","anchor":"cc","children":[]},{"title":"Palavras-chave","anchor":"keywords","children":[]}]},{"title":"Fechando Tickets","anchor":"closing-tickets","children":[]},{"title":"Como eu posso ajudar com a triagem?","anchor":"how-can-i-help-with-triaging","children":[]},{"title":"Bisseccionando uma regressão","anchor":"bisecting-a-regression","children":[]}],"breadcrumbs":[{"docname":"internals/index","title":"Funcionamento interno do Projeto Django","url":"/pt-br/5.2/internals/"},{"docname":"internals/contributing/index","title":"Contribuindo com o Django","url":"/pt-br/5.2/internals/contributing/"}],"prev":{"docname":"internals/contributing/bugs-and-features","title":"Relatando bugs e solicitando funcionalidades","url":"/pt-br/5.2/internals/contributing/bugs-and-features/"},"next":{"docname":"internals/mailing-lists","title":"Mailing lists and Forum","url":"/pt-br/5.2/internals/mailing-lists/"},"formats":{"html":"/pt-br/5.2/internals/contributing/triaging-tickets/","markdown":"/pt-br/5.2/internals/contributing/triaging-tickets.md","json":"/pt-br/5.2/internals/contributing/triaging-tickets.json"},"source":"https://github.com/django/django/blob/stable/5.2.x/docs/internals/contributing/triaging-tickets.txt","official":"https://docs.djangoproject.com/pt-br/5.2/internals/contributing/triaging-tickets/","inVersions":["6.1","6.0","5.2","5.1","5.0","4.2","4.1","4.0","3.2","3.1","3.0","2.2","2.1","2.0","1.11","1.10","1.9"],"inLocales":["en","sv","zh-hans","ga","fr","ja","id","it","pt-br","ko","es","el","pl"]}