All content in this course uses:

6.3 - Sharing your Projects & Database

In this lesson, you will learn how to build your projects so that they’re playable outside of the Unity interface. First, you will install the necessary export modules to be able to publish your projects. After that, you will build your project as a standalone app to be played on Mac or PC computers. Finally, you will export your project for WebGL and even upload it to a game sharing site so that you can send it to your friends and family.

Your project will be exported and playable as a standalone app on Mac/PC or for embedding online.

Before we can export our projects, we need to add the “Export Modules” that will allow us to export for particular platforms.

 to the version of Unity you have used in the course

 and wait for the installation to complete

Install export Modules

Now that we have the export modules installed, we can put them to use and export one of our projects

 the project you would like to build (could be a prototype or your personal project)

 and adjust any settings you want, including making it “Windowed”, “Resizable”, and whether or not you want to enable the “Display Resolution Dialog”

, name your project, and save it inside a new folder inside your Create with Code folder called “

 your game to test it out, then if you want, 

Build your game for Mac or Windows

 are formal tests executed to verify if a system satisfies its business requirements. They require the entire application to be up and running and focus on replicating user behaviors. But they can also go further and measure the performance of the system and reject changes if certain goals are not met.

Now that you are finishing your project, create your final test script and do the following: 

Find a fellow learner on the QA Pathway to acceptance test your game using the final test script and use your database to track, report, and prioritize bugs.  

If you can't find a fellow learner - ask a family member or friend to play your game. Watch them play it and as they play take exploratory testing notes of them playing it. Use those notes to go back and test yourself and track, report and prioritize bugs. 

Fix any and all bugs and save your project.

Acceptance Testing

Since it is pretty hard to distribute your games on Mac or Windows, it’s a good idea to make your projects available online by building for WebGL.

, then save in your “Builds” folder with “

 to run your project (you may have to try opening with different browsers) 

Right-click on your WebGL build folder and 

Build your game for WebGL

As you learned when you started on the QA pathway, 

 checks the behaviors of the system when it is under significant load. These tests are non-functional and can have the various form to understand the reliability, stability, and availability of the platform. For instance, it can be observing response times when executing a high number of requests, or seeing how the system behaves with a significant of data. Once you have optimized your project do the following: 

Create a test script to test various performance features of your project now that it is published as WebGL. 

In the database you created performance test your game to make sure it's running efficiently and effectively as possible. Track, log and prioritize any final bugs you find. 

Go back to Step 3 and prepare your final build. 

Performance Testing

Lesson Recap

We would love to see what you've come up with in your project and your QA database. Please take a screenshot of the views of your project and database or do a screen-recording walking us through it, then post it here to share your creation. 

Unity Version 2019.3