Skip to content

Test Plan For Asset Loading

JivalX edited this page Oct 19, 2023 · 4 revisions

Test Plan for Asset Loading

This test plan outlines the structure for testing similar classes in the Sprint 4. It serves as a template for documenting the testing process for various classes that uses Asset Loading .

The classes that run the Test For Asset Loading are :

  • NavigationBackgroundTest.java
  • ControlsScreenDisplayTest.java
  • ControlsScreenTest.java
  • SettingsScreenTest.java
  • InitialScreenDisplayTest.java
  • ReturntoPlanetDisplayTest.java
  • TutorialScreenTest.java

Test Setup

Before running the test case, the necessary setup is performed:

  • The LibGDX application is mocked to run in a headless desktop environment to prevent graphics-related issues during testing.
  • An instance of the GdxGame is created.
  • A set of loaded assets is initialized.

Test Case: testAssetLoading()

This test case verifies whether the texture asset is successfully loaded in the provided classes.

Test Steps:

  1. Create an instance of the provided class.
  2. Retrieve the texture from the created instance of your class.
  3. Verify that the texture is not null, indicating successful asset loading.
image

Conclusion

This wiki page provides documentation for classes and its associated test cases, testAssetLoading(). By running this test case, we ensure that the class can reliably load the texture asset, maintaining the reliability and correctness of the components in the game.

Contributors

Clone this wiki locally