How/when can a UIViewController return self.storyboard nil.
I am trying to instantiate a ViewController with:
self.storyboard!.instantiateViewControllerWithIdentifier
But self.storyboard is nil?
Note: the plist is set to the right storyboard.
Per the Apple documentation, UIViewController's storyboard property represents the storyboard from which the view controller originated. It returns an optional UIStoryboard instance which is nil if the view controller was not instantiated from a storyboard.
Try this :
let localStoryboard = UIStoryboard(name: "Main", bundle: nil)
Related
In my main storyboard I have 1 Navigation controller and subsequent swift file NavigationCtr.swift.
The viewController is in different xib.
Now I want to push my viewController from the NavigationCtr class.
let vcFirst = FirstViewController(nibName: "FirstViewController", bundle: nil)
self.navigationController!.pushViewController(vcFirst, animated: true)
I am getting a exception
fatal error: unexpectedly found nil while unwrapping an Optional value
So when I trying to print from viewDidLoad
print(self.navigationController)
in NavigationCtr.swift class it is giving nil. So nothing works
I created a new project in objective C and it works fine.
Attached the storyboard image
Any hint in the direct direction is highly appreciated.
Note : - I am new to swift
the main issue was using the self.navigationController
As my storyboard only had navigationController I should just self keyword.
as below
let vcFirst = FirstViewController(nibName: "FirstViewController", bundle: nil)
self.pushViewController(vcFirst, animated: true)
For the first controller, set it as rootController instead of push (show).
self.navigationController = UINavigationController(rootViewController: vcFirst)
Or set its view controllers
self.navigationController = UINavigationController()
navigationController.setViewControllers([vcfirst], animated: true)
Here is a screenshot from Xcode 8.2:
If the function does not exist, how do you add identifier to a view controller these days?
Use instead instantiateViewController(withIdentifier:) when you would like a ViewController and attach a view from the storyboard (UIStoryboard Id Identifier)
instantiateInitialViewController() is to instantiate the default view initial, this function takes no argument and is something you wouldn't usually do programmatically.
let sb = UIStoryboard(name: "", bundle: Bundle.main)
sb.instantiateViewController(withIdentifier: "blue")
I got put into a project that has the following declaration:
UIStoryboard(name: "Main", bundle: nil).instantiateViewControllerWithIdentifier("asdf") as! AsdfViewController
I've always used storyboard! to do this. It is my understanding that storyboard! will always give me UIStoryboard(name: "Main", bundle: nil). Is this a dangerous assumption to make?
I know that you may want to use the official constructor for UIStoryboard if you wanted to reference a different storyboard file, but is it safe to abbreviate it to storyboard! if you are sure that the VC you wish to instantiate is part of Main.storyboard?
If you are calling self.storyboard from a view controller that is on another storyboard file, it will give reference to that particular storyboard; not the main storyboard. By mentioning:
UIStoryboard(name: "Main", bundle: nil)
You can make sure that you are referencing the main storyboard always.
In following situations:
Have only one storyboard file
Instantiate a view controller which is also included in the current view controller's storyboard
using self.storyboard is enough.
How do we load a UITabBarController from NIB?
for UIViewControllers we could easily do this
let viewController = SubclassOfViewController(nibName: "SubclassOfAViewController", bundle: nil);
But I could not find any similar method to load a UITabBarController which is from Nib
Any thoughts?
Thank you
Edit: I am not using Storyboards
If you are using storyboard
let tabbarController = [[UIStoryboard storyboardWithName:#"Main"bundle:NULL] instantiateViewControllerWithIdentifier:#"SubclassOfAViewController"];
where SubclassOfAViewController is identifier.
Else
let viewController = SubclassOfViewController(nibName: "SubclassOfAViewController", bundle: nil)
This method is fine. Since UITabbarController is a subclass of UIViewController there is no need of separate method here in subclass
I am trying to add some unit tests to my project to test view controllers. However I seem to be having problems with seemingly simple things. I have created a sample project which I will refer to. https://github.com/pangers/ViewControllerTesting
The sample contains a UINavigationController as the initial view controller. The root view controller of the UINavigationController is FirstViewController. There is a button on FirstViewController that segues to SecondViewController. In SecondViewController there is an empty textfield.
The two tests I am trying to add are:
1) Check button title in FirstViewController is "Next Screen".
2) Check textfield in SecondViewController is empty, "".
I have heard reports of adding your swift files to both the main target and the test target is not good practice. But rather it is better to make whatever you want to access in your tests public and import the main target into the tests. So that is what I have done. (I have also set the "Defines Module" for the main target to YES as that is what I have read in a few articles aswell).
In FirstViewControllerTests I have instantiated the first view controller with the following:
var viewController: FirstViewController!
override func setUp() {
let storyboard = UIStoryboard(name: "Main", bundle: NSBundle(forClass: self.dynamicType))
let navigationController = storyboard.instantiateInitialViewController() as UINavigationController
viewController = navigationController.topViewController as FirstViewController
viewController.viewDidLoad()
}
And I have added the test:
func testCheckButtonHasTextNextScreen() {
XCTAssertEqual(viewController.button.currentTitle!, "Next Screen", "Button should say Next Screen")
}
Similarly, for SecondViewControllerTest, I have set it up using:
var secondViewController:SecondViewController!
override func setUp() {
let storyboard = UIStoryboard(name: "Main", bundle: NSBundle(forClass: self.dynamicType))
let navigationController = storyboard.instantiateInitialViewController() as UINavigationController
let firstviewController = navigationController.topViewController as FirstViewController
firstviewController.performSegueWithIdentifier("FirstToSecond", sender: nil)
secondViewController = navigationController.topViewController as SecondViewController
secondViewController.viewDidLoad()
}
And the test:
func testTextFieldIsBlank() {
XCTAssertEqual(secondViewController.textField.text, "", "Nothing in textfield")
}
They both fail and I am not too sure as to why. My suspicion is that the way I am instantiating the view controllers is not correct. Is the best way to instantiate the view controllers is to use the storyboard (just like it would if it were to run in real life)? Or is it acceptable to be instantiated via:
var viewController = FirstViewController()
What are you guys' experience with TDD and view controllers in swift?
I am using Swift with XCode 6.1.1.
Thanks in advance.
Solved
Ok after considering the answers from modocache and Mike Taverne, I've found my solution and I've learnt a few things which I will write down below.
1) I made anything class/method/variable that I want to test public. I do not need to add the swift files to the test target.
2) I only needed to set "Defines Module" for the "Main" target (as opposed to the "Test" target or the entire project)
3) When instantiating the storyboard, the bundle should be set to nil rather than NSBundle(forClass: self.dynamicType), otherwise tests will fail.
4) As modocache stated, it is good to give your view controller's a StoryboardID and instantiate them like so:
viewController = storyboard.instantiateViewControllerWithIdentifier("FirstViewController") as FirstViewController
However, instantiating the view controller like this ONLY instantiates the view controller alone, and not any navigation controllers that it may be embedded in. That means, attempting to do
XCTAssertFalse(viewController.navigationController!.navigationBarHidden, "Bar should show by default")
will result in a nil exception. I confirmed this with
XCTAssertNil(viewController.navigationController?, "navigation controller doesn't exist")
which resulted in a successful test.
Since I wanted to check the state of the navigation bar in FirstViewController, you must instantiate the view controller like so:
let storyboard = UIStoryboard(name: "Main", bundle: nil)
let navigationController = storyboard.instantiateInitialViewController() as UINavigationController
viewController = navigationController.topViewController as FirstViewController
Now performing the test
XCTAssertFalse(viewController.navigationController!.navigationBarHidden, "nav bar should be showing by default")
results in a successful test.
5) let _ = viewController.view does indeed trigger viewDidLoad() which was confirmed by a test
6) let _ = viewController.view does not trigger viewWillAppear(), and I presume anything afterwards aswell. viewController.viewWillAppear(false/true) needs to be called manually to trigger it (Confirmed by a test).
Hopefully this will be of help to people. I will push the updated project to GitHub (link above) if anyone would like to play around with it.
Update #2
After all the above, I still could not figure out how to transition from the first view controller to the second view controller (so that I may test navigation bar properties in SecondViewControllerTests.swift). I tried
let storyboard = UIStoryboard(name: "Main", bundle: nil)
let nc = storyboard.instantiateInitialViewController() as UINavigationController
let firstVC = nc.topViewController as FirstViewController
firstVC.performSegueWithIdentifier("FirstToSecond", sender: nil)
secondVC = nc.topViewController as SecondViewController
which caused an error.
I also tried
let storyboard = UIStoryboard(name: "Main", bundle: nil)
let nc = storyboard.instantiateInitialViewController() as UINavigationController
let firstVC = nc.topViewController as FirstViewController
firstVC.toSecondVCButton.sendActionsForControlEvents(UIControlEvents.TouchUpInside)
secondVC = nc.topViewController as SecondViewController
which did not work.
I eventually tried
let storyboard = UIStoryboard(name: "Main", bundle: nil)
let nc = storyboard.instantiateInitialViewController() as UINavigationController
vc = storyboard.instantiateViewControllerWithIdentifier("Second") as SecondViewController
nc.pushViewController(vc, animated: false)
let _ = vc.view
vc.viewWillAppear(false)
which worked perfectly with my tests (allowed me to access navigation bar properties)!
I agree with #MikeTaverne's answer: I prefer accessing -[UIViewController view] in order to trigger -[UIViewController viewDidLoad], rather than calling it directly. See if the test failures for FirstViewController go away once you use this instead:
viewController = navigationController.topViewController as FirstViewController
let _ = viewController.view
I'd also recommend giving both view controllers identifiers in your storyboard. This will allow you to instantiate them directly, without accessing them via UINavigationController:
var secondViewController: SecondViewController!
override func setUp() {
let storyboard = UIStoryboard(name: "Main", bundle: NSBundle(forClass: self.dynamicType))
secondViewController = storyboard.instantiateViewControllerWithIdentifier("SecondViewController")
as SecondViewController
let _ = secondViewController.view
}
Check out my talk on testing UIViewController at Brooklyn Swift for details: https://vimeo.com/115671189#t=37m50s (my presentation begins around the 37'50" mark).
I've begun unit testing view controllers recently, and it poses some unique challenges.
One challenge is getting the view to load. Looking at your set up for FirstViewController, you are trying to do this with viewController.viewDidLoad().
My suggestion is to replace that line with this:
let dummy = viewController.view
Accessing the .view property will force the view to load. This will trigger the .viewDidLoad in your ViewController, so don't call that method explicitly in your test.
This approach is considered hacky by some people, but it is simple and effective. (See Clean way to force view to load subviews early)
As an aside, I am finding the best way to test view controllers is to move as much code out of the view controllers as possible into other classes that are more easily tested.
If your view controller is defined in a storyboard, then you need to instantiate it that way for your outlets to be set up properly. Trying to initialize it like an ordinary class won't work.