codelite unittest++/UnitTest++.h: no such file or directory2019 Community Moderator ElectionLinker errors with codelite, unittest++ and g++ on linuxHow can I get “Copy to Output Directory” to work with Unit Tests?Running unittest with typical test directory structurenetbeans mysql connector No such file or directory (MinGW)Eclipse Cannot find the UnitTest++ libraryIncluding C++ Library in Ubuntu/NetbeansLinker errors with codelite, unittest++ and g++ on linuxanother main.cpp inside test directoryHow to build and run multiple main cpp files in CodeLite IDE that are in different Projects or within same projects?Codelite linker undefined reference errorcppunittest.h no such file or directory

What should I do when a paper is published similar to my PhD thesis without citation?

What is the purpose of a disclaimer like "this is not legal advice"?

Use Mercury as quenching liquid for swords?

How do we create new idioms and use them in a novel?

Rationale to prefer local variables over instance variables?

The preposition for the verb (avenge) - avenge sb/sth (on OR from) sb

How do I raise a figure (placed with wrapfig) to be flush with the top of a paragraph?

Has a sovereign Communist government ever run, and conceded loss, on a fair election?

Having the player face themselves after the mid-game

ESPP--any reason not to go all in?

How to install round brake pads

Optimal Proportions for Flying Humans

What do you call someone who likes to pick fights?

How to educate team mate to take screenshots for bugs with out unwanted stuff

Is this Paypal Github SDK reference really a dangerous site?

What to do if my university does not offer any advanced math courses?

How can a demon take control of a human body during REM sleep?

Why do we say 'Pairwise Disjoint', rather than 'Disjoint'?

Logistic regression BIC: what's the right N?

Writing text next to a table

Is there stress on two letters on the word стоят

How exactly does an Ethernet collision happen in the cable, since nodes use different circuits for Tx and Rx?

The (Easy) Road to Code

Are E natural minor and B harmonic minor related?



codelite unittest++/UnitTest++.h: no such file or directory



2019 Community Moderator ElectionLinker errors with codelite, unittest++ and g++ on linuxHow can I get “Copy to Output Directory” to work with Unit Tests?Running unittest with typical test directory structurenetbeans mysql connector No such file or directory (MinGW)Eclipse Cannot find the UnitTest++ libraryIncluding C++ Library in Ubuntu/NetbeansLinker errors with codelite, unittest++ and g++ on linuxanother main.cpp inside test directoryHow to build and run multiple main cpp files in CodeLite IDE that are in different Projects or within same projects?Codelite linker undefined reference errorcppunittest.h no such file or directory










0















I am trying to do unit testing with C++/Codelite. I have UnitTest++ plugin installed from codelite-plugins package (Ubuntu 18.04). I can also see this:



$ ls -la /usr/include | grep Unit
drwxr-xr-x 3 root root 4096 Mar 2 11:47 UnitTest++

$ sudo dpkg -l | grep unittest++
ii libunittest++-dev 2.0.0-2 amd64 unit testing framework for c++, static library and headers
ii libunittest++2:amd64 2.0.0-2 amd64 unit testing framework for c++, runtime library


So I create a test project in Codelite and I add this:



#include <unittest++/UnitTest++.h> // This line and main are auto-created

TEST(SanityTest)

CHECK_EQUAL(1, 1);


int main(int argc, char **argv)

return UnitTest::RunAllTests();



Now I would expect test results after I press CTRL+F5. But when I do, I only get a popup window saying there are no tests:



enter image description here



I also noticed that when I go to Build > Build Project I get an error message:




fatal error: unittest++/UnitTest++.h: No such file or directory




I also found THIS ANSWER and tried different variation of console commands as per answer/comments there, but I always get the same no such file or directory error.



Any idea what I am missing?



EDIT:



Build log as per Stephen's Newell request:



/bin/sh -c '/usr/bin/make -j8 -e -f Makefile'
----------Building project:[ Test - Debug ]----------
make[1]: Entering directory '/home/callmebob/Documents/workspace-codelite/cpp/Test'
/usr/bin/g++ -c "/home/callmebob/Documents/workspace-codelite/cpp/Test/main.cpp" -g -o Debug/main.cpp.o -I. -I/usr/include/unittest++
/home/callmebob/Documents/workspace-codelite/cpp/Test/main.cpp:1:10: fatal error: unittest++/UnitTest++.h: No such file or directory
#include "unittest++/UnitTest++.h"
^~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
Test.mk:95: recipe for target 'Debug/main.cpp.o' failed
make[1]: *** [Debug/main.cpp.o] Error 1
make[1]: Leaving directory '/home/callmebob/Documents/workspace-codelite/cpp/Test'
Makefile:4: recipe for target 'All' failed
make: *** [All] Error 2
====2 errors, 0 warnings====


Also if I right-click the project, go to Settings > Compiler, I can see:




Included Paths = /usr/include/unittest++











share|improve this question
























  • Have you verified the files actually exist? I don't use ubuntu (or any apt-based distro), but they're probably under /usr/include. Also, please include the full compilation line (it's probably above the error you already provided).

    – Stephen Newell
    Mar 6 at 13:27











  • Build log added. Also on top of my post there is output "ls -la /usr/include" where you can see UnitTest++. It's with capitals and doesn't have .h at the end. I tired including with no .h with the same results though.

    – callmebob
    Mar 6 at 13:37











  • Based on your ls output, my hunch is that the directory name in your code is incorrect. Try changing the first line to #include <UnitTest++/UnitTest.h> (you may want to verify the contents of /usr/include/UnitTest++ first).

    – Stephen Newell
    Mar 6 at 13:42











  • @StephenNewell: you were correct. I had to change it to <UnitTest++/UnitTest++.h> at the end. From here, I was able to build, but now on CTRL+F5 I was getting nothing at all. Seems like I have to do CTRL+F9 (Build and run) to get results - not sure why, but it works. If you want add an answer and I will accept it as you pointed me to the correct direction.

    – callmebob
    Mar 6 at 13:55











  • Glad it worked!

    – Stephen Newell
    Mar 6 at 14:24















0















I am trying to do unit testing with C++/Codelite. I have UnitTest++ plugin installed from codelite-plugins package (Ubuntu 18.04). I can also see this:



$ ls -la /usr/include | grep Unit
drwxr-xr-x 3 root root 4096 Mar 2 11:47 UnitTest++

$ sudo dpkg -l | grep unittest++
ii libunittest++-dev 2.0.0-2 amd64 unit testing framework for c++, static library and headers
ii libunittest++2:amd64 2.0.0-2 amd64 unit testing framework for c++, runtime library


So I create a test project in Codelite and I add this:



#include <unittest++/UnitTest++.h> // This line and main are auto-created

TEST(SanityTest)

CHECK_EQUAL(1, 1);


int main(int argc, char **argv)

return UnitTest::RunAllTests();



Now I would expect test results after I press CTRL+F5. But when I do, I only get a popup window saying there are no tests:



enter image description here



I also noticed that when I go to Build > Build Project I get an error message:




fatal error: unittest++/UnitTest++.h: No such file or directory




I also found THIS ANSWER and tried different variation of console commands as per answer/comments there, but I always get the same no such file or directory error.



Any idea what I am missing?



EDIT:



Build log as per Stephen's Newell request:



/bin/sh -c '/usr/bin/make -j8 -e -f Makefile'
----------Building project:[ Test - Debug ]----------
make[1]: Entering directory '/home/callmebob/Documents/workspace-codelite/cpp/Test'
/usr/bin/g++ -c "/home/callmebob/Documents/workspace-codelite/cpp/Test/main.cpp" -g -o Debug/main.cpp.o -I. -I/usr/include/unittest++
/home/callmebob/Documents/workspace-codelite/cpp/Test/main.cpp:1:10: fatal error: unittest++/UnitTest++.h: No such file or directory
#include "unittest++/UnitTest++.h"
^~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
Test.mk:95: recipe for target 'Debug/main.cpp.o' failed
make[1]: *** [Debug/main.cpp.o] Error 1
make[1]: Leaving directory '/home/callmebob/Documents/workspace-codelite/cpp/Test'
Makefile:4: recipe for target 'All' failed
make: *** [All] Error 2
====2 errors, 0 warnings====


Also if I right-click the project, go to Settings > Compiler, I can see:




Included Paths = /usr/include/unittest++











share|improve this question
























  • Have you verified the files actually exist? I don't use ubuntu (or any apt-based distro), but they're probably under /usr/include. Also, please include the full compilation line (it's probably above the error you already provided).

    – Stephen Newell
    Mar 6 at 13:27











  • Build log added. Also on top of my post there is output "ls -la /usr/include" where you can see UnitTest++. It's with capitals and doesn't have .h at the end. I tired including with no .h with the same results though.

    – callmebob
    Mar 6 at 13:37











  • Based on your ls output, my hunch is that the directory name in your code is incorrect. Try changing the first line to #include <UnitTest++/UnitTest.h> (you may want to verify the contents of /usr/include/UnitTest++ first).

    – Stephen Newell
    Mar 6 at 13:42











  • @StephenNewell: you were correct. I had to change it to <UnitTest++/UnitTest++.h> at the end. From here, I was able to build, but now on CTRL+F5 I was getting nothing at all. Seems like I have to do CTRL+F9 (Build and run) to get results - not sure why, but it works. If you want add an answer and I will accept it as you pointed me to the correct direction.

    – callmebob
    Mar 6 at 13:55











  • Glad it worked!

    – Stephen Newell
    Mar 6 at 14:24













0












0








0








I am trying to do unit testing with C++/Codelite. I have UnitTest++ plugin installed from codelite-plugins package (Ubuntu 18.04). I can also see this:



$ ls -la /usr/include | grep Unit
drwxr-xr-x 3 root root 4096 Mar 2 11:47 UnitTest++

$ sudo dpkg -l | grep unittest++
ii libunittest++-dev 2.0.0-2 amd64 unit testing framework for c++, static library and headers
ii libunittest++2:amd64 2.0.0-2 amd64 unit testing framework for c++, runtime library


So I create a test project in Codelite and I add this:



#include <unittest++/UnitTest++.h> // This line and main are auto-created

TEST(SanityTest)

CHECK_EQUAL(1, 1);


int main(int argc, char **argv)

return UnitTest::RunAllTests();



Now I would expect test results after I press CTRL+F5. But when I do, I only get a popup window saying there are no tests:



enter image description here



I also noticed that when I go to Build > Build Project I get an error message:




fatal error: unittest++/UnitTest++.h: No such file or directory




I also found THIS ANSWER and tried different variation of console commands as per answer/comments there, but I always get the same no such file or directory error.



Any idea what I am missing?



EDIT:



Build log as per Stephen's Newell request:



/bin/sh -c '/usr/bin/make -j8 -e -f Makefile'
----------Building project:[ Test - Debug ]----------
make[1]: Entering directory '/home/callmebob/Documents/workspace-codelite/cpp/Test'
/usr/bin/g++ -c "/home/callmebob/Documents/workspace-codelite/cpp/Test/main.cpp" -g -o Debug/main.cpp.o -I. -I/usr/include/unittest++
/home/callmebob/Documents/workspace-codelite/cpp/Test/main.cpp:1:10: fatal error: unittest++/UnitTest++.h: No such file or directory
#include "unittest++/UnitTest++.h"
^~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
Test.mk:95: recipe for target 'Debug/main.cpp.o' failed
make[1]: *** [Debug/main.cpp.o] Error 1
make[1]: Leaving directory '/home/callmebob/Documents/workspace-codelite/cpp/Test'
Makefile:4: recipe for target 'All' failed
make: *** [All] Error 2
====2 errors, 0 warnings====


Also if I right-click the project, go to Settings > Compiler, I can see:




Included Paths = /usr/include/unittest++











share|improve this question
















I am trying to do unit testing with C++/Codelite. I have UnitTest++ plugin installed from codelite-plugins package (Ubuntu 18.04). I can also see this:



$ ls -la /usr/include | grep Unit
drwxr-xr-x 3 root root 4096 Mar 2 11:47 UnitTest++

$ sudo dpkg -l | grep unittest++
ii libunittest++-dev 2.0.0-2 amd64 unit testing framework for c++, static library and headers
ii libunittest++2:amd64 2.0.0-2 amd64 unit testing framework for c++, runtime library


So I create a test project in Codelite and I add this:



#include <unittest++/UnitTest++.h> // This line and main are auto-created

TEST(SanityTest)

CHECK_EQUAL(1, 1);


int main(int argc, char **argv)

return UnitTest::RunAllTests();



Now I would expect test results after I press CTRL+F5. But when I do, I only get a popup window saying there are no tests:



enter image description here



I also noticed that when I go to Build > Build Project I get an error message:




fatal error: unittest++/UnitTest++.h: No such file or directory




I also found THIS ANSWER and tried different variation of console commands as per answer/comments there, but I always get the same no such file or directory error.



Any idea what I am missing?



EDIT:



Build log as per Stephen's Newell request:



/bin/sh -c '/usr/bin/make -j8 -e -f Makefile'
----------Building project:[ Test - Debug ]----------
make[1]: Entering directory '/home/callmebob/Documents/workspace-codelite/cpp/Test'
/usr/bin/g++ -c "/home/callmebob/Documents/workspace-codelite/cpp/Test/main.cpp" -g -o Debug/main.cpp.o -I. -I/usr/include/unittest++
/home/callmebob/Documents/workspace-codelite/cpp/Test/main.cpp:1:10: fatal error: unittest++/UnitTest++.h: No such file or directory
#include "unittest++/UnitTest++.h"
^~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
Test.mk:95: recipe for target 'Debug/main.cpp.o' failed
make[1]: *** [Debug/main.cpp.o] Error 1
make[1]: Leaving directory '/home/callmebob/Documents/workspace-codelite/cpp/Test'
Makefile:4: recipe for target 'All' failed
make: *** [All] Error 2
====2 errors, 0 warnings====


Also if I right-click the project, go to Settings > Compiler, I can see:




Included Paths = /usr/include/unittest++








c++ unit-testing codelite unittest++






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 6 at 13:35







callmebob

















asked Mar 6 at 13:07









callmebobcallmebob

2,83621631




2,83621631












  • Have you verified the files actually exist? I don't use ubuntu (or any apt-based distro), but they're probably under /usr/include. Also, please include the full compilation line (it's probably above the error you already provided).

    – Stephen Newell
    Mar 6 at 13:27











  • Build log added. Also on top of my post there is output "ls -la /usr/include" where you can see UnitTest++. It's with capitals and doesn't have .h at the end. I tired including with no .h with the same results though.

    – callmebob
    Mar 6 at 13:37











  • Based on your ls output, my hunch is that the directory name in your code is incorrect. Try changing the first line to #include <UnitTest++/UnitTest.h> (you may want to verify the contents of /usr/include/UnitTest++ first).

    – Stephen Newell
    Mar 6 at 13:42











  • @StephenNewell: you were correct. I had to change it to <UnitTest++/UnitTest++.h> at the end. From here, I was able to build, but now on CTRL+F5 I was getting nothing at all. Seems like I have to do CTRL+F9 (Build and run) to get results - not sure why, but it works. If you want add an answer and I will accept it as you pointed me to the correct direction.

    – callmebob
    Mar 6 at 13:55











  • Glad it worked!

    – Stephen Newell
    Mar 6 at 14:24

















  • Have you verified the files actually exist? I don't use ubuntu (or any apt-based distro), but they're probably under /usr/include. Also, please include the full compilation line (it's probably above the error you already provided).

    – Stephen Newell
    Mar 6 at 13:27











  • Build log added. Also on top of my post there is output "ls -la /usr/include" where you can see UnitTest++. It's with capitals and doesn't have .h at the end. I tired including with no .h with the same results though.

    – callmebob
    Mar 6 at 13:37











  • Based on your ls output, my hunch is that the directory name in your code is incorrect. Try changing the first line to #include <UnitTest++/UnitTest.h> (you may want to verify the contents of /usr/include/UnitTest++ first).

    – Stephen Newell
    Mar 6 at 13:42











  • @StephenNewell: you were correct. I had to change it to <UnitTest++/UnitTest++.h> at the end. From here, I was able to build, but now on CTRL+F5 I was getting nothing at all. Seems like I have to do CTRL+F9 (Build and run) to get results - not sure why, but it works. If you want add an answer and I will accept it as you pointed me to the correct direction.

    – callmebob
    Mar 6 at 13:55











  • Glad it worked!

    – Stephen Newell
    Mar 6 at 14:24
















Have you verified the files actually exist? I don't use ubuntu (or any apt-based distro), but they're probably under /usr/include. Also, please include the full compilation line (it's probably above the error you already provided).

– Stephen Newell
Mar 6 at 13:27





Have you verified the files actually exist? I don't use ubuntu (or any apt-based distro), but they're probably under /usr/include. Also, please include the full compilation line (it's probably above the error you already provided).

– Stephen Newell
Mar 6 at 13:27













Build log added. Also on top of my post there is output "ls -la /usr/include" where you can see UnitTest++. It's with capitals and doesn't have .h at the end. I tired including with no .h with the same results though.

– callmebob
Mar 6 at 13:37





Build log added. Also on top of my post there is output "ls -la /usr/include" where you can see UnitTest++. It's with capitals and doesn't have .h at the end. I tired including with no .h with the same results though.

– callmebob
Mar 6 at 13:37













Based on your ls output, my hunch is that the directory name in your code is incorrect. Try changing the first line to #include <UnitTest++/UnitTest.h> (you may want to verify the contents of /usr/include/UnitTest++ first).

– Stephen Newell
Mar 6 at 13:42





Based on your ls output, my hunch is that the directory name in your code is incorrect. Try changing the first line to #include <UnitTest++/UnitTest.h> (you may want to verify the contents of /usr/include/UnitTest++ first).

– Stephen Newell
Mar 6 at 13:42













@StephenNewell: you were correct. I had to change it to <UnitTest++/UnitTest++.h> at the end. From here, I was able to build, but now on CTRL+F5 I was getting nothing at all. Seems like I have to do CTRL+F9 (Build and run) to get results - not sure why, but it works. If you want add an answer and I will accept it as you pointed me to the correct direction.

– callmebob
Mar 6 at 13:55





@StephenNewell: you were correct. I had to change it to <UnitTest++/UnitTest++.h> at the end. From here, I was able to build, but now on CTRL+F5 I was getting nothing at all. Seems like I have to do CTRL+F9 (Build and run) to get results - not sure why, but it works. If you want add an answer and I will accept it as you pointed me to the correct direction.

– callmebob
Mar 6 at 13:55













Glad it worked!

– Stephen Newell
Mar 6 at 14:24





Glad it worked!

– Stephen Newell
Mar 6 at 14:24












1 Answer
1






active

oldest

votes


















1














Based on your ls output, it looks like you should change your first line to this:



#include <UnitTest++/UnitTest++.h>


I'm not sure why the answer you linked to worked with a lowercase directory name; the examples in the project documentation all use the mixed-case directory name.






share|improve this answer























  • Yes, that's a bit weird with the lowercase. My initial code was also auto-generated with lowercase, like in my example. Probably best if I report a bug.

    – callmebob
    Mar 6 at 14:42










Your Answer






StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55023862%2fcodelite-unittest-unittest-h-no-such-file-or-directory%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














Based on your ls output, it looks like you should change your first line to this:



#include <UnitTest++/UnitTest++.h>


I'm not sure why the answer you linked to worked with a lowercase directory name; the examples in the project documentation all use the mixed-case directory name.






share|improve this answer























  • Yes, that's a bit weird with the lowercase. My initial code was also auto-generated with lowercase, like in my example. Probably best if I report a bug.

    – callmebob
    Mar 6 at 14:42















1














Based on your ls output, it looks like you should change your first line to this:



#include <UnitTest++/UnitTest++.h>


I'm not sure why the answer you linked to worked with a lowercase directory name; the examples in the project documentation all use the mixed-case directory name.






share|improve this answer























  • Yes, that's a bit weird with the lowercase. My initial code was also auto-generated with lowercase, like in my example. Probably best if I report a bug.

    – callmebob
    Mar 6 at 14:42













1












1








1







Based on your ls output, it looks like you should change your first line to this:



#include <UnitTest++/UnitTest++.h>


I'm not sure why the answer you linked to worked with a lowercase directory name; the examples in the project documentation all use the mixed-case directory name.






share|improve this answer













Based on your ls output, it looks like you should change your first line to this:



#include <UnitTest++/UnitTest++.h>


I'm not sure why the answer you linked to worked with a lowercase directory name; the examples in the project documentation all use the mixed-case directory name.







share|improve this answer












share|improve this answer



share|improve this answer










answered Mar 6 at 14:24









Stephen NewellStephen Newell

3,97111721




3,97111721












  • Yes, that's a bit weird with the lowercase. My initial code was also auto-generated with lowercase, like in my example. Probably best if I report a bug.

    – callmebob
    Mar 6 at 14:42

















  • Yes, that's a bit weird with the lowercase. My initial code was also auto-generated with lowercase, like in my example. Probably best if I report a bug.

    – callmebob
    Mar 6 at 14:42
















Yes, that's a bit weird with the lowercase. My initial code was also auto-generated with lowercase, like in my example. Probably best if I report a bug.

– callmebob
Mar 6 at 14:42





Yes, that's a bit weird with the lowercase. My initial code was also auto-generated with lowercase, like in my example. Probably best if I report a bug.

– callmebob
Mar 6 at 14:42



















draft saved

draft discarded
















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55023862%2fcodelite-unittest-unittest-h-no-such-file-or-directory%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

AWS Lex not identifying response if by a variable The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) The Ask Question Wizard is Live! Data science time! April 2019 and salary with experienceEnforcing custom enumeration in AWS LEX for slot valuesHow to give response based on user response in Amazon Lex?Intercepting AWS Lambda Response to a AWS Lex QueryLex chat bot error: Reached second execution of fulfillment lambda on the same utteranceamazon lex showing invalid responseLambda response send back to Lex slot?Response card in Amazon lexAmazon Lex - Lambda response return HTML to botHow can I solve 424 (Failed Dependency) (python) obtained from Amazon lex?

Алба-Юлія

Захаров Федір Захарович