Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Appian ACD201 Exam - Topic 3 Question 8 Discussion

Actual exam question for Appian's ACD201 exam
Question #: 8
Topic #: 3
[All ACD201 Questions]

You're performing System Integration Testing on a client's application that integrates with an external system.

In this instance, you're testing the application's interactions with external integrations to ensure that data is being handled correctly between the two systems. However, this step has been done manually and is time-consuming.

What should you do to make this process more efficient?

Show Suggested Answer Hide Answer
Suggested Answer: C

FitNesse for Appian is designed for automated functional testing of Appian workflows, including those that call external integrations. By building repeatable FitNesse test scripts that drive the end-to-end process, you can automatically verify that data is correctly sent to - and returned from - the external system each time, greatly reducing the manual effort of system-integration testing.


Contribute your Thoughts:

0/2000 characters
Aliza
22 days ago
C ensures workflows are functioning as expected. Automation is the future!
upvoted 0 times
...
Shonda
27 days ago
B could reveal bottlenecks. We need to know how it performs under load.
upvoted 0 times
...
Tammi
1 month ago
A is efficient for integration checks. Quick feedback is key!
upvoted 0 times
...
Izetta
1 month ago
C sounds good too. Automated testing can save a lot of time.
upvoted 0 times
...
Brent
1 month ago
Definitely A) for quick and effective testing!
upvoted 0 times
...
Luis
2 months ago
Wait, can FitNesse really handle all those integrations?
upvoted 0 times
...
Ranee
2 months ago
C) could really speed things up with automation!
upvoted 0 times
...
Della
2 months ago
I think B) is overkill for just integration testing.
upvoted 0 times
...
Olive
3 months ago
A) sounds like a solid plan for API testing!
upvoted 0 times
...
Leana
3 months ago
Integrating with external systems can be a real headache. Glad there are tools to make it less painful.
upvoted 0 times
...
Latonia
3 months ago
Postman, Appian-Locust, FitNesse... the options are making my head spin! I need a coffee break.
upvoted 0 times
...
Brittani
3 months ago
FitNesse for Appian? Sounds like a good way to automate the functional testing. Definitely worth considering.
upvoted 0 times
...
Crista
3 months ago
Appian-Locust for performance testing? That's an interesting approach. I'd have to look into that more.
upvoted 0 times
...
Elin
3 months ago
Option A seems like the way to go. Postman can really streamline the integration testing process.
upvoted 0 times
...
Stefany
4 months ago
I feel like automating with Postman would save a lot of time, but I also remember that we need to ensure the test cases are well-defined to get accurate results.
upvoted 0 times
...
Sylvia
4 months ago
I practiced a similar question where we had to choose between manual and automated testing tools. I think using Appian-Locust could help with performance, but I'm not sure if it's the best fit for this scenario.
upvoted 0 times
...
Alline
4 months ago
I'm not entirely sure about FitNesse. I think it was mentioned as a tool for functional testing, but I can't recall how it specifically applies to integrations.
upvoted 0 times
...
Kanisha
4 months ago
I'm leaning towards option C with FitNesse for Appian. Automating the functional testing on the workflows that include the integrated systems seems like it would save a lot of time in the long run.
upvoted 0 times
...
Arlen
4 months ago
Option B with Appian-Locust could be really useful for testing the performance of the system integrations. Simulating multiple users interacting with the external systems simultaneously would help identify any bottlenecks or issues.
upvoted 0 times
...
Carolann
4 months ago
I remember we discussed using Postman for API testing in class. It seems like a straightforward way to automate those integration tests.
upvoted 0 times
...
Ahmed
5 months ago
I prefer B. Performance testing is crucial for user experience.
upvoted 0 times
...
Kanisha
5 months ago
I think A is the best choice. Postman makes API testing straightforward.
upvoted 0 times
...
Peggy
5 months ago
I think a combination of options A and C would be the most comprehensive approach. Using Postman for the API testing and FitNesse for the automated functional testing would cover all the bases.
upvoted 0 times
...
Mickie
5 months ago
I'm a bit confused on the differences between the options. Can someone clarify the pros and cons of each approach? I want to make sure I understand the best way to tackle this efficiently.
upvoted 0 times
...
Carlton
6 months ago
I think option A sounds like the best approach here. Using Postman to test the integrations with the external system and Appian's APIs would be a great way to make the process more efficient and automated.
upvoted 0 times
Ashton
1 day ago
I think automation is key here, A is the way to go!
upvoted 0 times
...
Lovetta
6 days ago
I’ve used Postman before, it saves so much time.
upvoted 0 times
...
Dustin
11 days ago
Definitely! It simplifies the whole process.
upvoted 0 times
...
Magdalene
17 days ago
I agree, Postman is super efficient for API testing.
upvoted 0 times
...
Glen
5 months ago
Plus, it’s easy to set up test cases in Postman.
upvoted 0 times
...
...

Save Cancel