Struct XCTestExpectation

Source

pub struct XCTestExpectation { /* private fields */ }

Expand description

Expectations represent specific conditions in asynchronous testing.

Implementations§

Source §

impl XCTestExpectation

Source

pub fn initWithDescription( this: Allocated<Self>, expectation_description: &NSString, ) -> Retained<Self>

Designated initializer, requires a nonnull description of the condition the expectation is checking.

Source

pub fn expectationDescription(&self) -> Retained<NSString>

The human readable string used to describe the expectation in log output and test reports.

Source

pub fn setExpectationDescription(&self, expectation_description: &NSString)

Setter for expectationDescription.

This is copied when set.

Source

pub fn isInverted(&self) -> bool

If an expectation is set to have inverted behavior, then fulfilling it will have a similar effect that failing to fulfill a conventional expectation has, as handled by the waiter and its delegate. Furthermore, waiters that wait on an inverted expectation will allow the full timeout to elapse and not report timeout to the delegate if it is not fulfilled.

Source

pub fn setInverted(&self, inverted: bool)

Setter for isInverted.

Source

pub unsafe fn expectedFulfillmentCount(&self) -> NSUInteger

The expectedFulfillmentCount is the number of times -fulfill must be called on the expectation in order for it to report complete fulfillment to its waiter. By default, expectations have an expectedFufillmentCount of 1. This value must be greater than 0 and is not meaningful if combined with @ inverted.

This property is not atomic.

§Safety

This might not be thread-safe.

Source

pub unsafe fn setExpectedFulfillmentCount( &self, expected_fulfillment_count: NSUInteger, )

Setter for expectedFulfillmentCount.

§Safety

This might not be thread-safe.

Source

pub unsafe fn assertForOverFulfill(&self) -> bool

If set, calls to fulfill() after the expectation has already been fulfilled - exceeding the fulfillment count - will raise. This is the legacy behavior of expectations created through APIs on XCTestCase but is not enabled for expectations created using XCTestExpectation initializers.

This property is not atomic.

§Safety

This might not be thread-safe.

Source

pub unsafe fn setAssertForOverFulfill(&self, assert_for_over_fulfill: bool)

Setter for assertForOverFulfill.

§Safety

This might not be thread-safe.

Source

pub fn fulfill(&self)

Call -fulfill to mark an expectation as having been met. It’s an error to call -fulfill on an expectation more times than its expectedFulfillmentCount value specifies, or when the test case that vended the expectation has already completed. If assertForOverFulfill is set when either of these occur, -fulfill will raise an exception.

Source §

impl XCTestExpectation

Methods declared on superclass NSObject.

Source

pub fn init(this: Allocated<Self>) -> Retained<Self>

Source

pub fn new() -> Retained<Self>

Methods from Deref<Target = NSObject>§

Source

pub fn doesNotRecognizeSelector(&self, sel: Sel) -> !

Handle messages the object doesn’t recognize.

See Apple’s documentation for details.

Methods from Deref<Target = AnyObject>§

Source

pub fn class(&self) -> &'static AnyClass

Dynamically find the class of this object.

§Panics

May panic if the object is invalid (which may be the case for objects returned from unavailable init/new methods).

§Example

Check that an instance of NSObject has the precise class NSObject.

use objc2::ClassType;
use objc2::runtime::NSObject;

let obj = NSObject::new();
assert_eq!(obj.class(), NSObject::class());

Source

pub unsafe fn get_ivar<T>(&self, name: &str) -> &T
where T: Encode,

👎Deprecated: this is difficult to use correctly, use Ivar::load instead.

Use Ivar::load instead.

§Safety

The object must have an instance variable with the given name, and it must be of type T.

See Ivar::load_ptr for details surrounding this.

Source

pub fn downcast_ref<T>(&self) -> Option<&T>
where T: DowncastTarget,

Attempt to downcast the object to a class of type T.

This is the reference-variant. Use Retained::downcast if you want to convert a retained object to another type.

§Mutable classes

Some classes have immutable and mutable variants, such as NSString and NSMutableString.

When some Objective-C API signature says it gives you an immutable class, it generally expects you to not mutate that, even though it may technically be mutable “under the hood”.

So using this method to convert a NSString to a NSMutableString, while not unsound, is generally frowned upon unless you created the string yourself, or the API explicitly documents the string to be mutable.

See Apple’s documentation on mutability and on isKindOfClass: for more details.

§Generic classes

Objective-C generics are called “lightweight generics”, and that’s because they aren’t exposed in the runtime. This makes it impossible to safely downcast to generic collections, so this is disallowed by this method.

You can, however, safely downcast to generic collections where all the type-parameters are AnyObject.

§Panics

This works internally by calling isKindOfClass:. That means that the object must have the instance method of that name, and an exception will be thrown (if CoreFoundation is linked) or the process will abort if that is not the case. In the vast majority of cases, you don’t need to worry about this, since both root objects NSObject and NSProxy implement this method.

§Examples

Cast an NSString back and forth from NSObject.

use objc2::rc::Retained;
use objc2_foundation::{NSObject, NSString};

let obj: Retained<NSObject> = NSString::new().into_super();
let string = obj.downcast_ref::<NSString>().unwrap();
// Or with `downcast`, if we do not need the object afterwards
let string = obj.downcast::<NSString>().unwrap();

Try (and fail) to cast an NSObject to an NSString.

use objc2_foundation::{NSObject, NSString};

let obj = NSObject::new();
assert!(obj.downcast_ref::<NSString>().is_none());

Try to cast to an array of strings.

use objc2_foundation::{NSArray, NSObject, NSString};

let arr = NSArray::from_retained_slice(&[NSObject::new()]);
// This is invalid and doesn't type check.
let arr = arr.downcast_ref::<NSArray<NSString>>();

This fails to compile, since it would require enumerating over the array to ensure that each element is of the desired type, which is a performance pitfall.

Downcast when processing each element instead.

use objc2_foundation::{NSArray, NSObject, NSString};

let arr = NSArray::from_retained_slice(&[NSObject::new()]);

for elem in arr {
    if let Some(data) = elem.downcast_ref::<NSString>() {
        // handle `data`
    }
}