BitBucket

Bitbucket is a web-based platform for hosting and collaborating on code repositories using either Git or Mercurial version control systems. It offers features for source code management, including repositories, pull requests, code reviews, issue tracking, and more. Bitbucket is commonly used by software development teams to store, share, and manage their codebases securely in the cloud, making it a crucial part of many software development workflows.

Quality Modeller recognizes the vital role Bitbucket plays in these workflows and offers robust integration with it. The integration features a dedicated connector that is capable of both importing automation page objects from Bitbucket  and exporting generated automation code back to a Bitbucket   repository. This bidirectional exchange ensures that the testing process is fully integrated with the broader software development workflow.

The import function streamlines the process of integrating existing page objects into Quality Modeller's testing environment, saving time and effort. Simultaneously, the export function allows the automation code generated within Quality Modeller to be stored and managed within the familiar Bitbucket  environment. This seamless integration not only enhances the efficiency of the test creation and management process but also ensures that the generated automation code is readily available for future development and testing efforts. In this way, Quality Modeller's Bitbucket integration helps teams maintain continuity and consistency across their software development and testing processes.

To learn more about connecting to Bitbucket, please refer to our documentation below. You will need the following information in order to configure the connection:

The configure connector dialogue has three tabs:

1. Details: Where the connector type and name is set.
2. Connection: The connection and configuration information for the connector.
3. Traceability: Shows which Automation Frameworks in the workspace use this BitBucket connector.

Select BitBucket from the Connector Type dropdown and give this a recognisable Profile Name. Also choose if you would like this connector to be shared among all users in the workspace.

In the connection tab, configure the following information:

1. Username: The user you would like to commit code with in BitBucket. To find your exact user name in the Atlassian platform, navigate to Personal Settings -> General -> Account Settings.
2. Password: This will be an App Password created in BitBucket. To configure a password, navigate to Personal Settings -> Access Management -> App Passwords.
3. Git Repository: The Git repository URL, you will be able to copy this from BitBucket. This will include the '.git' at the end of the URL.
4. Commit Branch: Defines the branch you want to commit code to in BitBucket, this must already exist in BitBucket before committing code from Quality Modeller.
5. Pull Request: This is an On or Off toggle.
   1. If OFF, code will be pushed directly to the branch specified above.
   2. If ON, then a second field will show called Pull Request Target Branch. Here you can specify a branch to create, that will in turn create the pull request to the main commit branch. This is very useful for code reviews before committing to a repository.

There are a number of Advanced optional fields:

1. Author (Override): Allows you to override the Author of the code commit. This can be hard coded or you use [UserEmail] to apply the current logged in users email.
2. Name (Override): Allows you to override the Name associated with a code commit. This can be hard coded or you use [UserFullName] to apply the current logged in users name.
3. Git Library: This field lets you choose the underlying library that handles Git operations. This can be set to LibGit2Sharp, a C# wrapper around the native Git library, or Native.
4. HTTP Proxy URL: This field is where you specify the URL of an HTTP proxy server if your network requires it to access external resources over HTTP. For example, http://proxy.mycompany.com:8080. In this example, the proxy server’s URL is proxy.mycompany.com, and it’s using port 8080. The proxy would forward your tool’s HTTP requests to BitBucket. 
5. HTTPS Proxy URL: This field is used to specify the URL of an HTTPS proxy, which handles encrypted HTTPS traffic. For example, https://secure-proxy.mycompany.com:443. In this example, the proxy server is secure-proxy.mycompany.com, and it is listening on port 443 (the standard port for HTTPS traffic) 

Finally, there are a number of User Actions that can be applied to the connector.

1. Validate: Takes the Saved Username and API Key credentials and tests that a connection can be established and the user can be logged in.
2. Reset: Clears the temporary copy of the Git repository that Quality Modeller stores, this can be useful to run as a troubleshooting step if something goes wrong.
3. Pull: Pulls the latest version of the Git repository into Quality Modeller.
4. Cancel: Cancels any changes made to the configurations.
5. Save: Saves changes.