The switch statement is not yielding any results

Question

The switch statement is not yielding any results

I am currently working on a test that involves processing a string through a switch statement. However, I am facing an issue where the integer value set in the case of the switch statement is not being passed correctly. As a result, the subsequent if statement fails to work as expected.

Here is the object for the switch:

var appsNotPurchased = 0;
this.checksHomeSublevel = function(mmCode) {
    browser.get('https://iplan-qa.meetingmatrix.com/Home/Index/' + mmCode);
    marketingObjects.level.getText().then(function(text) {
      var homeText = text;
      browser.get('https://iplan-qa.meetingmatrix.com/Home/Apps/' + mmCode);
      expect($('div.apps-subscription > span').getText()).toEqual('iPlan Level: ' + homeText);
      switch (homeText) {
        case 'Select':
          console.log(homeText);
          appsNotPurchased = 6;
          return appsNotPurchased;
          break;
        case 'Content':
          console.log(homeText);
          appsNotPurchased = 0 || 1 || 2 || 3 || 4 || 5 || 6;
          return appsNotPurchased;
          break;
      }


    });

Below is the testSpec describe function:

describe('should upload media: ', function() {

  it('should select add media', function() {
    var mmCode = "ACC0572";
    var appsNotPurchased = appsObjects.checksHomeSublevel(mmCode);
    appsObjects.checksSubLevelSelect(mmCode, appsNotPurchased);
  });

});

The object that receives the value:

    this.checksSubLevelSelect = function(mmCode, appsNotPurchased) {

      //checks and counts the apps
      apps.count().then(function(count) {
        expect(count).toEqual(7);
        for (var i = 0; i < count; i++) {
          if (appsPlace == appsNotPurchased) {
            //perform certain actions here
          } else {
            //perform other actions here
          }
          appsPlace++;
        }
      });
    };

javascript angularjs selenium-webdriver switch-statement protractor

Answer 1

Answer №1

To improve your code, it is recommended to return an object instead of using the || statement. Additionally, ensure that the return statement is placed outside the switch statement rather than inside it.

An easy solution would be to utilize a global variable named appsNotPurchased to store the value and then access it in your test specifications without needing to return it, although this may not adhere to best coding practices.
Another solution is to return a promise from the function since Protractor executes asynchronously.

Here is an example implementing the second solution:

this.checksHomeSublevel = function(mmCode) {
    var getval = marketingObjects.level.getText().then(function(text) {
        switch (homeText) {
          case 'Select':
            console.log(homeText);
            appsNotPurchased = [6];
            break;
          case 'Content':
            console.log(homeText);
            appsNotPurchased = [0, 1, 2, 3, 4, 5, 6]; //either use array or object
            break;
          default:
            console.log("Default");
        }
        return appsNotPurchased;
    });
    return protractor.promise.fulfilled(getval);
};

Then, you can use it as a promise in your spec:

appsObjects.checksHomeSublevel(mmCode).then(function(appsNotPurchased){
    appsObjects.checksSubLevelSelect(mmCode, appsNotPurchased);
});

Incorporate the result into your function now:

this.checksSubLevelSelect = function(mmCode, appsNotPurchased) {

      //counts the apps
      apps.count().then(function(count) {
        expect(count).toEqual(7);
        for (var i = 0; i < count; i++) {
          if (appsPlace == appsNotPurchased[i]) {
            //does something here
          } else {
            //does something here
          }
          appsPlace++;
        }
      });
    };

I hope this explanation proves helpful.

Answer 2

To improve your code, it is recommended to return an object instead of using the || statement. Additionally, ensure that the return statement is placed outside the switch statement rather than inside it.

An easy solution would be to utilize a global variable named appsNotPurchased to store the value and then access it in your test specifications without needing to return it, although this may not adhere to best coding practices.
Another solution is to return a promise from the function since Protractor executes asynchronously.

Here is an example implementing the second solution:

this.checksHomeSublevel = function(mmCode) {
    var getval = marketingObjects.level.getText().then(function(text) {
        switch (homeText) {
          case 'Select':
            console.log(homeText);
            appsNotPurchased = [6];
            break;
          case 'Content':
            console.log(homeText);
            appsNotPurchased = [0, 1, 2, 3, 4, 5, 6]; //either use array or object
            break;
          default:
            console.log("Default");
        }
        return appsNotPurchased;
    });
    return protractor.promise.fulfilled(getval);
};

Then, you can use it as a promise in your spec:

appsObjects.checksHomeSublevel(mmCode).then(function(appsNotPurchased){
    appsObjects.checksSubLevelSelect(mmCode, appsNotPurchased);
});

Incorporate the result into your function now:

this.checksSubLevelSelect = function(mmCode, appsNotPurchased) {

      //counts the apps
      apps.count().then(function(count) {
        expect(count).toEqual(7);
        for (var i = 0; i < count; i++) {
          if (appsPlace == appsNotPurchased[i]) {
            //does something here
          } else {
            //does something here
          }
          appsPlace++;
        }
      });
    };

I hope this explanation proves helpful.

The switch statement is not yielding any results

Answer №1

Similar questions

The onChange method in React is failing to execute within the component

The Route.get() function in Node.js is expecting a callback function, but instead received an unexpected object of type

Text displaying as actionable icons

Is your Jquery validation malfunctioning?

Upon introducing the CSS loader into the webpack configuration, TinyMCE unexpectedly ceases to function

Tips on waiting for the user to click before proceeding with the rest of the automation process

React error: Unable to iterate through items because property 'forEach' is undefined

How can you make a button in Vue only visible after all API calls have successfully retrieved the data?

Enabling the apple-mobile-web-app-capable feature prevents SVG touches from registering

Angular-schema-form utilizes computed values to dynamically generate form fields based on

Trouble with minified scripts on a particular server

Guide to selecting the initial index in search drop down with selenium using C#

Two separate entities link to a shared occurrence

Is it possible to use a custom filter along with data-ng-model? Problem arises when attempting to bind a custom filter with data-ng-model

After saving any HTML, SCSS, or TS file, Angular 12 does not compile immediately

Gathering information from a website where the URL remains constant even after clicking on a specific button

Singleton pattern for iFrames sharing the same origin

What is the best way to ensure my jQuery plugin is up to date?

Eliminating duplicate loading of jQuery in Django SmartSelect

Eliminate parameter from URL