Juls Terobias

<h4>Ver 0.9.8.3 Beta</h4>
<h3>AutoQA</h3>
<p>Automate the testing of your WordPress sites and plugins without the need for coding.</p>
<p>AutoQA is a simple automation plugin designed to improve your regression testing process, reducing testing time by up to 70%. It comes equipped with a variety of useful testing steps and a WordPress-specific test runner, ensuring seamless integration and efficient performance within your WordPress environment.</p>
<p><a href="https://julsterobias.github.io/autoqa/" rel="nofollow ugc">Website</a> | <a href="https://julsterobias.github.io/autoqa/documentation" rel="nofollow ugc">Documentation</a></p>
<h3>Key Features</h3>
<h3>Flows</h3>
<p>Each flow acts as a customizable test case, allowing users to simulate and verify various processes within their application. A flow consists of a series of steps, which represent specific actions or interactions. Whether it’s a simple user journey or a complex workflow, this feature enables detailed testing by breaking down tasks into manageable steps, ensuring that every aspect of your process works seamlessly from start to finish.</p>
<h3>Steps</h3>
<p>The Steps feature in the Flow plugin is designed to automate user actions, emulating how a real user would interact with your website or WordPress application. Each step represents a specific action, such as clicking a button, filling out a form, or navigating through pages. These steps are built within a Flow, where they combine to form a comprehensive test case.</p>
<p>By using Steps, you can easily automate repetitive user interactions, allowing the plugin to test your site or app seamlessly. This saves you time and ensures that all key functionalities are thoroughly verified without manual intervention.</p>
<p>With Steps, you can ensure a smoother, error-free experience for your users, all while simplifying your testing process.</p>
<h3>Runners</h3>
<p>Designed to efficiently handle and execute each step of your flow in sequence. It ensures that all steps are processed systematically, checking whether each step passes or fails based on predefined criteria. The Runner automatically records the results, including pass/fail status, directly into the database for easy tracking and review. This feature simplifies the management of test cases, making it easier to monitor progress and identify issues at any step in the process.</p>
<h3>Steps</h3>
<ul>
<li>Start – This step initiates the test by directing the browser or test framework to navigate to a specific URL provided by the user.</li>
</ul>
<h3>Input</h3>
<ul>
<li>Click – Simulates a user clicking on an element (e.g., a button or a link) on the web page.</li>
<li>Hover – Simulates a user hovering their mouse over a particular element on the webpage.</li>
<li>Manual Input – Provides an opportunity for the user to input values or perform actions manually during the test run.</li>
<li>Set Text – Automatically fills in a text field or text area with specified input.</li>
<li>Set Select – Simulates selecting an option from a dropdown or selection field.</li>
<li>Send Keys – Simulates the sending keys to field.</li>
<li>Drag and Drop – Simulates the drag and drop event.</li>
<li>Empty Field – Empty the text field.</li>
<li>Scroll – Emulates the action of scrolling through a page or a specific element.</li>
<li>Reload – Simulates refreshing or reloading the current web page.</li>
</ul>
<h3>Upload File</h3>
<ul>
<li>Upload Image – Generates test image and simulate the upload event.</li>
<li>Upload PDF – Generates test PDF and simulate the upload event.</li>
</ul>
<h3>Check</h3>
<ul>
<li>Check Page Title – Verifies that the title of the current webpage matches the expected value.</li>
<li>Check Text – Verifies that specific text is present within a non-input field element, such as a div, span, or p.</li>
<li>Check Value – Validates the value of form field elements like input, textarea, or select.</li>
<li>Check Attribute – Validates that a specific attribute of an element has the expected value.</li>
<li>Check Element Count – Verifies the number of occurrences of certain elements (e.g., li, div, option) on the page matches the expected count.</li>
<li>Check Visibility – Checks if a specified element is visible or hidden on the page.</li>
<li>Check Data – Validates data stored in the browser’s local or session storage, using a user-assigned name and value.</li>
</ul>
<h3>Delay</h3>
<ul>
<li>Delay – Pauses the execution of the test for a specified amount of time (in seconds).</li>
<li>Wait To – Pauses the test execution until a specific element performs a certain action (e.g., becomes visible, clickable, or contains text).</li>
</ul>
<h3>Data</h3>
<ul>
<li>Element Data – Stores the value or attribute of an element into a data variable for later use.</li>
<li>Store Data – Allows users to store dynamic data into a variable, which can include system-generated values like date and timestamp, or data extracted from elements.</li>
</ul>
<h3>WordPress</h3>
<ul>
<li>Check Meta – This step verifies specific metadata associated with a WordPress post, page, or custom post type. Users can define which meta keys and values to check, ensuring that expected metadata is present and correct.</li>
<li>Check Transient – This step inspects WordPress transients, which are temporary, cached data stored in the database. It checks if a specified transient exists and whether it holds the correct data, helping ensure that temporary data caching behaves as expected.</li>
<li>Check Scheduler – This step reviews scheduled tasks (cron jobs) in WordPress to confirm their existence</li>
<li>Check Post – This step validates specific details of a WordPress post, such as its title, content, status, or other attributes. It ensures that a particular post or custom post type is published, draft, or set up with the correct data as expected.</li>
</ul>


AutoQA

jack89ita

<p>When you modify a WordPress template, you might be affecting dozens of pages without even knowing it. <strong>Taiji Template Inspector</strong> gives you full visibility: instantly see which pages, posts and custom post types use each template — before you change a single line of code.</p>
<p>Designed for WordPress developers and agencies working on complex sites, it turns template management from a guessing game into a controlled, auditable process.</p>
<p><a href="https://github.com/Jack89ita/taiji-template-inspector" rel="nofollow ugc">View on GitHub</a></p>
<h4>What you can do</h4>
<ul>
<li><strong>See every page affected by any template</strong> — at a glance, sorted by usage count so the most impactful templates are always first</li>
<li><strong>Expand any template row</strong> to inspect the individual posts and pages assigned to it</li>
<li><strong>Open all impacted pages in one click</strong> — choose between frontend preview or backend editor</li>
<li><strong>Spot orphaned templates</strong> — files missing from the theme are automatically flagged, so you can clean up safely</li>
<li><strong>Export a full usage report as CSV</strong> for QA workflows and documentation</li>
<li><strong>Filter by language</strong> when using WPML or Polylang on multilingual sites</li>
<li><strong>Search templates instantly</strong> with the live search bar</li>
</ul>
<h4>Built for real projects</h4>
<p>Taiji Template Inspector is read-only and completely safe to use in production. It uses optimised database queries with WordPress transient caching to minimise performance impact, even on large sites with hundreds of pages and multiple custom post types.</p>
<p>No settings to configure. Install, activate, and find it under <strong>Tools <span aria-hidden="true" class="wp-exclude-emoji">→</span> Taiji Template Inspector</strong>.</p>
<h4>Who is this for?</h4>
<ul>
<li><strong>Developers</strong> maintaining or refactoring WordPress themes</li>
<li><strong>Agencies</strong> managing client sites with complex template structures</li>
<li><strong>QA teams</strong> who need to verify which pages are affected before deploying changes</li>
</ul>


Taiji Template Inspector

Instantly see which pages a template powers, so every change is intentional — never accidental.

AutoQA vs Taiji Template Inspector