Skip to content

Commit

Permalink
deploy: a62c178
Browse files Browse the repository at this point in the history
  • Loading branch information
@kpodemski
kpodemski committed Jan 22, 2024
1 parent 9cfdabd commit 210bd43
Show file tree
Hide file tree
Showing 35 changed files with 123 additions and 202 deletions.
43 changes: 0 additions & 43 deletions index.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -132,16 +132,6 @@ Notre engagement Dans l’intérêt de favoriser un environnement ouvert
So, let&amp;rsquo;s build a knowledge base. If you want to contribute to this page, please create a pull request for each module or theme you would like to propose, following the example:</description>
</item>

<item>
<title></title>
<link>https://www.prestashop-project.org/project-organization/quality-council/processes/pr-management/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

<guid>https://www.prestashop-project.org/project-organization/quality-council/processes/pr-management/</guid>
<description>Testing Pull Request How to test a PR manually You want to take care of a PR and you don&amp;rsquo;t know how to handle it, or you&amp;rsquo;ve simply forgotten how? No problem, this github page is for you.
1. Taking information from a PR One of the first things to do when starting a PR is to find out as much as possible about it. To do this, you&amp;rsquo;ll find this table at the start of each PR</description>
</item>

<item>
<title></title>
<link>https://www.prestashop-project.org/slack/apps-and-integrationsapps-and-integrations/</link>
Expand Down Expand Up @@ -216,17 +206,6 @@ We require from maintainers to take the necessary steps to make sure this accoun
Please note that severity is to be distinguished from priority. Indeed, severity is used to measure the negative impact that a bug has on a system, a feature, a component or on the project development.</description>
</item>

<item>
<title>How to contribute to UI tests</title>
<link>https://www.prestashop-project.org/project-organization/quality-council/processes/contribute-ui-tests/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

<guid>https://www.prestashop-project.org/project-organization/quality-council/processes/contribute-ui-tests/</guid>
<description>How to contribute to UI tests Introduction Branches The first question to ask when making a contribution is &amp;ldquo;Which branch should I target?&amp;rdquo;.
The rules are as follows:
The development branch for UI testing is the current development branch. The branch changes as soon as the final release is out. Differences between scenarios &amp;amp; tests Scenarios are the base of UI Tests. They are available on the PrestaShop Tests Documentation.</description>
</item>

<item>
<title>How to create merge Pull Requests active branches</title>
<link>https://www.prestashop-project.org/maintainers-guide/processes/creating-merge-pull-requests/</link>
Expand All @@ -238,28 +217,6 @@ Merge Pull Request Here is the explanation of how you should create your merge p
Clone the repository locally You’ll need to checkout/create branches for both your source branch and your target branch, or update them if you already have them locally git checkout -b 1.</description>
</item>

<item>
<title>How to Manage a release</title>
<link>https://www.prestashop-project.org/project-organization/quality-council/processes/release-manager/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

<guid>https://www.prestashop-project.org/project-organization/quality-council/processes/release-manager/</guid>
<description>How to create a Test Plan / Release Plan When a new release is made by the developers, a Test Plan and a Release Plan must be created on the QA side.
Although these tickets are currently created on an internal company Jira, the purpose of this documentation is to explain what information is needed to prepare the release, and how to obtain it, before carrying out a release.
1. Know the release The first thing to do is to find out about the release you&amp;rsquo;re going to test.</description>
</item>

<item>
<title>How to manage Issues</title>
<link>https://www.prestashop-project.org/project-organization/quality-council/processes/issue-management/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

<guid>https://www.prestashop-project.org/project-organization/quality-council/processes/issue-management/</guid>
<description>How to manage Issues This document details the processes in place for the position of &amp;ldquo;Issues Manager&amp;rdquo;, a rotating position within the QA community members.
The Issue Manager job Your job is to qualify issues submitted to the GitHub project. Good issues help us discover bugs and provide ideas to improve PrestaShop and the native modules. These are the three questions you must ask yourself:
Is the issue valid? The issue must be a bug report.</description>
</item>

<item>
<title>How to release a native module</title>
<link>https://www.prestashop-project.org/maintainers-guide/processes/release/native-module/</link>
Expand Down
21 changes: 6 additions & 15 deletions project-organization/quality-council/processes/contribute-ui-tests/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,7 @@
<head>
<meta charset="utf-8">
<title>How to contribute to UI tests | PrestaShop Project - Open Source e-Commerce platform</title>
<meta name="description" content="How to contribute to UI tests Introduction Branches The first question to ask when making a contribution is &ldquo;Which branch should I target?&rdquo;.
The rules are as follows:
The development branch for UI testing is the current development branch. The branch changes as soon as the final release is out. Differences between scenarios &amp; tests Scenarios are the base of UI Tests. They are available on the PrestaShop Tests Documentation."/>
<meta name="description" content=""/>

<link rel="canonical" href="https://www.prestashop-project.org/project-organization/quality-council/processes/contribute-ui-tests/" itemprop="url" />

Expand All @@ -28,17 +26,11 @@

<!-- Open Graph image and Twitter Card metadata -->
<meta name="twitter:title" content="How to contribute to UI tests"/>
<meta name="twitter:description" content="How to contribute to UI tests Introduction Branches The first question to ask when making a contribution is &ldquo;Which branch should I target?&rdquo;.
The rules are as follows:
The development branch for UI testing is the current development branch. The branch changes as soon as the final release is out. Differences between scenarios &amp; tests Scenarios are the base of UI Tests. They are available on the PrestaShop Tests Documentation."/>
<meta name="twitter:description" content=""/>
<meta property="og:title" content="How to contribute to UI tests" />
<meta property="og:description" content="How to contribute to UI tests Introduction Branches The first question to ask when making a contribution is &ldquo;Which branch should I target?&rdquo;.
The rules are as follows:
The development branch for UI testing is the current development branch. The branch changes as soon as the final release is out. Differences between scenarios &amp; tests Scenarios are the base of UI Tests. They are available on the PrestaShop Tests Documentation." />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://www.prestashop-project.org/project-organization/quality-council/processes/contribute-ui-tests/" /><meta property="article:section" content="project-organization" />

<meta property="article:modified_time" content="2023-07-31T14:21:10+02:00" />
<meta property="og:description" content="" />
<meta property="og:type" content="website" />
<meta property="og:url" content="https://www.prestashop-project.org/project-organization/quality-council/processes/contribute-ui-tests/" />



Expand Down Expand Up @@ -231,7 +223,7 @@




<section class="section">
<div class="container">
<div class="row mx-xl-2">
Expand Down Expand Up @@ -367,7 +359,6 @@ <h3 id="merge-of-the-pr">Merge of the PR</h3>




</main>


Expand Down
10 changes: 10 additions & 0 deletions project-organization/quality-council/processes/contribute-ui-tests/index.xml
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>How to contribute to UI tests on PrestaShop Project - Open Source e-Commerce platform</title>
<link>https://www.prestashop-project.org/project-organization/quality-council/processes/contribute-ui-tests/</link>
<description>Recent content in How to contribute to UI tests on PrestaShop Project - Open Source e-Commerce platform</description>
<generator>Hugo -- gohugo.io</generator>
<language>en-us</language><atom:link href="https://www.prestashop-project.org/project-organization/quality-council/processes/contribute-ui-tests/index.xml" rel="self" type="application/rss+xml" />
</channel>
</rss>
2 changes: 1 addition & 1 deletion project-organization/quality-council/processes/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -280,7 +280,7 @@ <h2 id="pull-request-management">Pull Request Management</h2>
<ul>
<li><a href="./pr-management">Testing Pull Request</a></li>
</ul>
<h2 id="software-testing">Software Testing</h2>
<h2 id="testing-with-vagrant">Testing with vagrant</h2>
<ul>
<li><a href="./test-pr-and-branches">How to test Pull Requests</a></li>
</ul>
Expand Down
43 changes: 0 additions & 43 deletions project-organization/quality-council/processes/index.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -6,48 +6,5 @@
<description>Recent content in Processes on PrestaShop Project - Open Source e-Commerce platform</description>
<generator>Hugo -- gohugo.io</generator>
<language>en-us</language><atom:link href="https://www.prestashop-project.org/project-organization/quality-council/processes/index.xml" rel="self" type="application/rss+xml" />
<item>
<title></title>
<link>https://www.prestashop-project.org/project-organization/quality-council/processes/pr-management/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

<guid>https://www.prestashop-project.org/project-organization/quality-council/processes/pr-management/</guid>
<description>Testing Pull Request How to test a PR manually You want to take care of a PR and you don&amp;rsquo;t know how to handle it, or you&amp;rsquo;ve simply forgotten how? No problem, this github page is for you.
1. Taking information from a PR One of the first things to do when starting a PR is to find out as much as possible about it. To do this, you&amp;rsquo;ll find this table at the start of each PR</description>
</item>

<item>
<title>How to contribute to UI tests</title>
<link>https://www.prestashop-project.org/project-organization/quality-council/processes/contribute-ui-tests/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

<guid>https://www.prestashop-project.org/project-organization/quality-council/processes/contribute-ui-tests/</guid>
<description>How to contribute to UI tests Introduction Branches The first question to ask when making a contribution is &amp;ldquo;Which branch should I target?&amp;rdquo;.
The rules are as follows:
The development branch for UI testing is the current development branch. The branch changes as soon as the final release is out. Differences between scenarios &amp;amp; tests Scenarios are the base of UI Tests. They are available on the PrestaShop Tests Documentation.</description>
</item>

<item>
<title>How to Manage a release</title>
<link>https://www.prestashop-project.org/project-organization/quality-council/processes/release-manager/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

<guid>https://www.prestashop-project.org/project-organization/quality-council/processes/release-manager/</guid>
<description>How to create a Test Plan / Release Plan When a new release is made by the developers, a Test Plan and a Release Plan must be created on the QA side.
Although these tickets are currently created on an internal company Jira, the purpose of this documentation is to explain what information is needed to prepare the release, and how to obtain it, before carrying out a release.
1. Know the release The first thing to do is to find out about the release you&amp;rsquo;re going to test.</description>
</item>

<item>
<title>How to manage Issues</title>
<link>https://www.prestashop-project.org/project-organization/quality-council/processes/issue-management/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

<guid>https://www.prestashop-project.org/project-organization/quality-council/processes/issue-management/</guid>
<description>How to manage Issues This document details the processes in place for the position of &amp;ldquo;Issues Manager&amp;rdquo;, a rotating position within the QA community members.
The Issue Manager job Your job is to qualify issues submitted to the GitHub project. Good issues help us discover bugs and provide ideas to improve PrestaShop and the native modules. These are the three questions you must ask yourself:
Is the issue valid? The issue must be a bug report.</description>
</item>

</channel>
</rss>
0 ...cil/processes/images/Issue_state_flow.jpg → ...issue-management/img/Issue_state_flow.jpg
View file
File renamed without changes
Loading

0 comments on commit 210bd43

Please sign in to comment.