joomla/Component-Builder
joomla/Component-Builder
39
23
Fork 11
Code Issues 82 Pull Requests Projects 4 Wiki Activity
Page: Beta Testing
Pages
001 Hello World with Joomla Component Builder 002 Intro to JCB 003 Installation of JCB 004 General Planning 005 Field Types 006 Basic Fields 007 Admin Views 008 Advanced Fields 009 Adding Admin Views to a Component 010 Component Settings 011 Component Scripts 012 Component FTP and more 013 dynamicGet 014 Adding dynamicGet to a Site View 015 Adding Templates and Layouts to a Site View 016 Template Setup 017 Layout Setup 018 Custom Admin Views 019 Adding Site Views to a Component 020 Adding Custom Admin Views to a Component 021 Tweaking MySQL Demo Data 022 Global Settings of Component Builder 023 Adding a custom time field 024 How to integrate the Create User Helper Method in your Components 025 How to use email helper in your components 026 How to setup a store message method along side the email helper class 027 How to ensure that a field is not escaped when added to list views 028 How to change exported values and setup custom import options 029 How to overwrite the custom fields 030 How to filter a list field based on association with another field 031 Automatic import of custom code during compilation in JCB 032 JCB manual custom code implementation 033 Export Import of fully mapped components 034 How to add Custom Buttons in JCB to your component Admin Area 035 Translation Mananger in JCB explained 036 Setting Site View Permission 037 Auto create SQL updates for Componets in JCB 038 Setup Site Edit View in JCB 039 Automated backup system in JCB 040 Adding Helper Structures to any JCB component 041 Upgrade to JCB v2.5.8 and using the new Admin View and Admin Fields 042 How to setup tabs after upgrade to v2.5.8 in JCB 043 Major Release of JCB v2.6.0 044 Hello World Component with Joomla Component Builder Creator Extended 045 Adding your own rule validation to a field in JCB 046 General overview of how community snippets work 047 Tutorial on forking JCB snippets so you can share your snippets with the rest of the Community 048 Tutorial on making a pull request at Joomla Component Builder Snippets 049 The New Library Manager Area 050 Easy Translation via excel 051 Dynamic Router Implementation Explained 052 Automated database updates in Joomla during development of a component 053 Quick Subform Demonstration 054 VDM Package Import Option 055 Dynamic File and Folder Inclusion concept 056 How to use the file field type to upload a file in JCB 057 Drag and Drop Upload functionality in JCB 058 The Quick Hello Word with JCB 059 Adding none database fields to an admin view 060 The custom dashboard option in JCB 061 Add or Remove Prefix to Component Name in Joomla Menu 062 Add your own JCB packages to the JCB Communty Directory 063 Proposed Collaborative Workflow in JCB 064 How to install jcb packages 065 JAB18 Using Joomla Component Builder 066 The new fields Area to make things easier 067 Adding Language String to your Component and get the Language Placeholder for dynamic use 068 Library Manager Anticipated Functionality 069 Join Fields in the admin list view with field relations 070 How to change the License Template in JCB 071 Reuse Custom Code 072 Setup Local Development Environment with Bitnami 073 JCB Fields Type Extended 074 How to add Joomla Custom Fields 075 Expand Custom Field Type Beyond The Default 076 A Quick Demonstration to Load a List of Items in a Site View 077 Run Expansion Explained 078 How to Add a Form to a Site View 079 Update the Site Form Field via URL Parameter 080 How to Add More Helper Methods to Your Components Helper Class 081 Easy Validation Rules for Fields in JCB 082 New Placeholders Feature 083 Manage a Components Global Config Option Field in Relation With Menu Params 084 Default Database Values can be set per Field Type Beta Testing Component Settings Develop a Joomla Component Guide to use the Component Builder Developing with Joomla Component Builder Home PHP Settings TIPS: Custom Code Using the JCB Demo Component While Building Your Local Development System
1 Beta Testing
Llewellyn edited this page 2023-04-02 22:46:41 +00:00
Table of Contents

Getting Started as a Joomla Component Builder Beta Tester

Overview

To help improve the stability and performance of Joomla Component Builder (JCB), the project needs more loyal testers. Beta testers will download, install, and test new beta versions of JCB, then report any issues they find. This document will guide you through the process of becoming a JCB beta tester.

Steps to become a JCB Beta Tester

  1. Join the JCB releases/update channel: https://t.me/jcb_updates
  2. Watch for beta releases from the Beta repo and download them.
  3. Install the downloaded beta version on a blank Joomla website.
  4. Perform a series of tasks and test the new features or changes.
  5. Report any issues you find on Gitea: https://git.vdm.dev/joomla/Component-Builder/issues and tag them with the Beta tag.
  6. Check for any open issues tagged with Beta before starting your testing.

How to Test

  1. Download the latest release from https://git.vdm.dev/joomla-beta/pkg-component-builder/archive/master.zip
  2. Install and test locally
  3. Report issues via ticket at https://git.vdm.dev/joomla/Component-Builder/issues

Change Logs

You can find change logs for each release in the following locations:

Review the change logs and commit history to understand which features/functions/areas have been updated and require testing.

Additional Tips and Detailed Steps

  1. Understanding changes: Keep an eye on the change logs in both the beta channel (https://git.vdm.dev/joomla-beta/com-componentbuilder/src/branch/master/CHANGELOG.md) and the stable channel (https://git.vdm.dev/joomla/Component-Builder/src/branch/staging/CHANGELOG.md). This can help you identify areas that require testing. Also, review the commit history to get a better understanding of the changes made, although this might be overwhelming for non-programmers.

  2. Compiling components: During the testing process, make sure to compile your components into a git repository. This will allow you to see what has changed and identify any issues. Make it a habit to compile and upload components to git after every update.

  3. Familiarize yourself with JCB's "Powers" feature: This is an advanced aspect of the platform that can significantly enhance your PHP programming capabilities. As the project evolves, more features will be introduced through Powers, so understanding this aspect is crucial for effective testing.

  4. Actively participate in the JCB updates channel: Join the JCB updates channel (https://t.me/jcb_updates) and stay up-to-date with the latest beta releases. Engage with the community, share your experiences, and provide valuable feedback to help improve the project.

  5. Using the release checking component: JCB has a release checking component (https://git.vdm.dev/joomla/com_release_checking) that can be used to mark and provide feedback on the tested features. This component can be installed on a Joomla system linked to Gitea, and accessed using your Gitea account. Utilize this tool to streamline the testing process and make it more efficient.

  6. Collaborate with fellow testers: Coordinate with other beta testers and share your testing experiences. Create a list of areas that need to be checked for each release and divide the tasks among the testers. This will ensure a comprehensive testing process and help identify potential issues more effectively.

  7. Reporting issues: If you find any issues during testing, report them at https://git.vdm.dev/joomla/Component-Builder/issues. Make sure to tag the issue with the "Beta" tag and check for existing issues with the same tag before submitting a new one. This will prevent duplicate issue reports and help the development team prioritize their tasks.

This guide assumes you have Git installed on your system. If you don't, please follow the official instructions on how to install Git: https://git-scm.com/book/en/v2/Getting-Started-Installing-Git

How to test the compiler (in the Octojoom setup):

Step 1: Initialize a Git Repository in Your Component's Target Folder (on your production instance)

  1. Open your command line interface or terminal.

  2. Navigate to the target folder of your component:

cd /path/to/your/component/target/folder
  1. Initialize a Git repository:
git init

Step 2: Commit Your Component's Initial State

  1. Add all the files in the target folder to the staging area:
git add .
  1. Commit the files with a meaningful message:
git commit -m "Initial commit of my component"

Step 3: Copy the Target Folder and Set up the Beta JCB Instance

  1. Copy the target folder to a new location that you can delete when you're done:
cp -R /path/to/your/component/target/folder /path/to/new/target/folder

  1. Set up your new blank install of the beta version of JCB to target this new folder.

  2. Import your component into the new JCB instance via the JCB package import area.

Step 4: Compile Your Component with the Beta JCB Instance

  1. Compile your component.

Step 5: Review Changes Made by the Beta JCB Instance

  1. In the command line interface or terminal, navigate to the new target folder:
cd /path/to/new/target/folder
  1. Check the status of the Git repository:
git status
  1. If there are any changes, add them to the staging area:
git add .
  1. Commit the changes with a message indicating that they were made by the beta JCB instance:
git commit -m "Changes made by beta JCB instance"
  1. To see the differences between the stable JCB instance and the beta JCB instance, use the git diff command:
git diff HEAD~1

This command will show the differences between the current commit (HEAD) and the previous commit (HEAD~1).

  1. Review the differences and note any changes that appear to break your Joomla component or that are no longer the same as your stable JCB instance.

Step 6: Report Any Issues

If you find any issues, report them to the JCB project by opening a new issue and tagging it with the Beta tag: https://git.vdm.dev/joomla/Component-Builder/issues

Remember that thorough testing is crucial to the project's success. The more active and committed testers we have, the more effectively JCB can evolve and improve. Happy testing!