Skip to main content

Setting Up BDD Testing for a Private Method

As I laid out in the start of this series, the goal here is testing beyond what I had been doing up to this point. The background is laid out here.

The next challenge was to test a private function. I didn't find a lot on this issue other than people were wondering how to do it although, admittedly, I didn't look for too long.

Here is the function which, except for the "private" part is the same as the previous method.

private function privateSimpleMath(numeric numA, numeric numB){
    return numA * numB;
}

I tried the same tests but got this (completely expected) error:


How to get around that without compromising the application in production? This might be simplistic and I'm open to debate but I simply extended my production component in another CFC and added a public function like this:

\tests\first\second\third\vanillaCFC\testVanilla.cfc:

component extends="testmods.first.second.third.vanillaCFC" {
// Place your content here    
    public function privateSimpleMath(numeric numA, numeric numB)
    {
        return super.privateSimpleMath(numA, numB);
    }
}


The Test Code

component extends="testbox.system.BaseSpec"{
   
/*********************************** LIFE CYCLE Methods ***********************************/
   // executes before all suites+specs in the run() method   function beforeAll(){
      testobj=createObject("component","pttests.first.second.third.vanillaCFC.testVanilla");
      testme=testobj.privateSimpleMath(9,8);
   }

   // executes after all suites+specs in the run() method   function afterAll(){
   }

/*********************************** BDD SUITES ***********************************/
   function run(){
   
      describe( "My test Suite", function(){
         
         it( "be a number", function(){
                expect( testme ).toBeTypeOf('numeric');
         });
         
         it( "should be 72", function(){
                expect( testme ).toBe(72);
         });
         
      });
      
   }
   
}

Process and Result

This is the same test as before with the only difference being that I instantiated the CFC which will live in my testing suite and has a public function and extends my actual CFC which will go into production and stays private.

Comments

Popular posts from this blog

Creating Stories and Tasks in Jira: Personas and our Software Development Team

Part of the CI/CD Development Series The next step is developing who is on our hypothetical development team. Given that it has a React front end and ColdFusion as the Server Side language, I came up with the following personas, all of which have their own needs and considerations for our development environment. I've listed all the jobs that need doing, not the people involved since, even on a small team or a team of one, these "hats" are all worn by someone, even if it's the same person. Personas for our Project Dev Ops Coordinator - The person responsible for smooth and accurate deployments CF Developer - The person responsible for the API and fulfillment code development and maintenance. React Developer - The person responsible for the front end development Database Coordinator - The person responsible for the schema, data, up time and, presumably the testing databases used by the developers. Lead Developer - The person responsible for coordinat...

More on Site Architecture / CI/CD / and Repos

We're starting to move from the high level overview and more into the details of our project.  Architecture We established that we using React as our front end technology and ColdFusion as our server side. At a more granular level, we'll be using React with Redux for our front end app and we want our server side to be not just "ajax" enabled but a true REST API. To this end, we're going to incorporate Coldbox from Ortus Solutions. Repos These two code bases have different needs, and possibly locations, when they are deployed. As a result, we're going to have two repositories: one for the React and another for the API. This will allow us to keep our code separated and cleaner all the way through to deployment.  For each of these repos, we'll follow the procedure we laid out previously with the MASTER branch being used to deploy to production and a DEVELOPMENT branch being used for active work which is then fed into the Master branch via pull requests.  Test...

CF: Scripting amidst the tags

Recently I had to do a quick "utility" page where I needed to see how many files from a directory listing had been recorded into a database. I've been writing about 98% of my CF code in script syntax but, since it was quick and easy, I did this quickly in tags because it was outputting directly to the browser. In doing so, I made an interesting discovery in that, when you use closures, even in tag based pages, you can write cfscript. Here's the example Get the directory listing:  < cfset alljs = directoryList(expandpath( '/src' ), true , "path" , "*.js" )> Get the database listings and convert it to an array < cfquery name = "alljsQ" datasource = "blah" > select * from sitefiles where filename like '%.js%' </ cfquery > < cfset recordedFiles = valuelist(alljsQ.filename).listToArray()> Use a filter function to weed out the files I'd already recorded < cfset missingFiles = alljs.fi...