Files
cappuccino/Tests/AppKit/CPSearchFieldTest.j
T
Alexandre Wilhelm 6fe9dae3d6 Fixed: AppKit unit-tests are not standalone
Previously, every AppKit tests used the same sharedApplication. Due to this implementation, a could not pass because a previous test made failed the current test. For instance, a test could fail because the window of the previous test resigned (just imagine a new window is the key window in the current test), and this resign could raise an error. The error was displayed for the current test thought this test was perfect !

We now instead of using sharedApplication create a new CPApplication per unit-test file in the class method setUp.
2015-07-07 14:12:19 -07:00

37 lines
865 B
Plaintext

@import <AppKit/AppKit.j>
@implementation CPSearchFieldTest : OJTestCase
{
CPSearchField _searchField;
}
+ (void)setUp
{
// This will init the global var CPApp which are used internally in the AppKit
[[CPApplication alloc] init];
}
- (void)setUp
{
_searchField = [[CPSearchField alloc] initWithFrame:CGRectMakeZero()];
}
- (void)testMakeCPSearchFieldInstance
{
[self assertNotNull:_searchField];
}
- (void)testRecentSearchesStartsEmpty
{
[self assertTrue:[[_searchField recentSearches] count] == 0 message:@"After instance creation we shouldn't have any recent searches."];
}
- (void)testSetRecentSearches
{
var searches = ["foo", "bar", "baz"];
[_searchField setRecentSearches:searches]
[self assertTrue:[[_searchField recentSearches] count] == 3 message:@"After setRecentSearches array doesn't include results"];
}
@end