You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
85 lines
3.2 KiB
Python
85 lines
3.2 KiB
Python
"""
|
|
All or portions of this file Copyright (c) Amazon.com, Inc. or its affiliates or
|
|
its licensors.
|
|
|
|
For complete copyright and license terms please see the LICENSE at the root of this
|
|
distribution (the "License"). All use of this software is governed by the License,
|
|
or, if provided, by the license below or the license accompanying this file. Do not
|
|
remove or modify any license notices. This file is distributed on an "AS IS" BASIS,
|
|
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
|
|
Test case ID : C12905528
|
|
Test Case Title : Check that user is warned if non-trigger collider component is used with force region
|
|
URL of the test case : https://testrail.agscollab.com/index.php?/cases/view/12905528
|
|
"""
|
|
|
|
|
|
# fmt: off
|
|
class Tests():
|
|
create_test_entity = ("Entity created successfully", "Failed to create Entity")
|
|
add_physx_force_region = ("PhysX Force Region component added", "Failed to add PhysX Force Region component")
|
|
add_physx_collider = ("PhysX Collider component added", "Failed to add PhysX Collider component")
|
|
warnings_found = ("Warnings found in logs", "No warnings found in logs")
|
|
# fmt: on
|
|
|
|
|
|
def run():
|
|
"""
|
|
Summary:
|
|
Create entity with PhysX Force Region component. Check that user is warned if new PhysX Collider component is
|
|
added to Entity.
|
|
|
|
Expected Behavior:
|
|
User is warned by message in the console that the PhysX Collider component was not marked as a trigger
|
|
|
|
Test Steps:
|
|
1) Load the empty level
|
|
2) Create test entity
|
|
3) Add PhysX Force Region component
|
|
4) Start the Tracer to catch any errors and warnings
|
|
5) Add PhysX Collider component to the Entity
|
|
6) Verify there is warning in the logs
|
|
|
|
Note:
|
|
- This test file must be called from the Open 3D Engine Editor command terminal
|
|
- Any passed and failed tests are written to the Editor.log file.
|
|
Parsing the file or running a log_monitor are required to observe the test results.
|
|
|
|
:return: None
|
|
"""
|
|
# Helper file Imports
|
|
import ImportPathHelper as imports
|
|
|
|
imports.init()
|
|
from utils import Report
|
|
from utils import TestHelper as helper
|
|
from utils import Tracer
|
|
from editor_entity_utils import EditorEntity
|
|
|
|
helper.init_idle()
|
|
# 1) Load the empty level
|
|
helper.open_level("Physics", "Base")
|
|
|
|
# 2) Create test entity
|
|
test_entity = EditorEntity.create_editor_entity("TestEntity")
|
|
Report.result(Tests.create_test_entity, test_entity.id.IsValid())
|
|
|
|
# 3) Add PhysX Force Region component
|
|
test_entity.add_component("PhysX Force Region")
|
|
Report.result(Tests.add_physx_force_region, test_entity.has_component("PhysX Force Region"))
|
|
|
|
# 4) Start the Tracer to catch any errors and warnings
|
|
with Tracer() as section_tracer:
|
|
# 5) Add the PhysX Collider component
|
|
test_entity.add_component("PhysX Collider")
|
|
Report.result(Tests.add_physx_collider, test_entity.has_component("PhysX Collider"))
|
|
|
|
# ) Verify there is warning in the logs
|
|
success_condition = section_tracer.has_warnings
|
|
# Checking if warning exist and the exact warning is caught in the expected lines in Test file
|
|
Report.result(Tests.warnings_found, success_condition)
|
|
|
|
|
|
if __name__ == "__main__":
|
|
run()
|